Step 4: Review

Engineers shall be objective and truthful in professional reports, statements, or testimony. They shall include all relevant and pertinent information in such reports, statements, or testimony, which should bear the date indicating when it was current.

Engineers shall act for each employer or client as faithful agents or trustees.

Engineers shall be guided in all their relations by the highest standards of honesty and integrity.

Engineers shall avoid all conduct or practice that deceives the public.

The Board cited this case to support the principle that engineers must overcome bias and remain objective, carefully analyzing all available information rather than skewing findings toward a predetermined conclusion.

It would be unethical for Engineer A to have found in the Owner's favor, contrary to his considered professional findings in this matter.

Beyond the Board's finding that it would be unethical for Engineer A to have found in the Owner's favor contrary to his professional findings, the structural design of the contract itself - which simultaneously designated Engineer A as both the Owner's faithful agent and the impartial interpreter of contract documents - created a role architecture that the Board did not fully interrogate. The ethical legitimacy of Engineer A's impartial ruling depends not only on the correctness of his technical finding but also on whether Engineer A adequately disclosed, at the time of contract formation, that his quasi-judicial dispute resolution role would require him to rule against the Owner's interests in cases where the evidence so demanded. Without such proactive disclosure, the Owner's subsequent complaint, while factually mistaken about the content of the loyalty obligation, may reflect a genuine informational asymmetry that Engineer A had some responsibility to prevent. The Board's conclusion is correct as far as it goes, but a more complete ethical analysis would require examining whether Engineer A fulfilled a pre-dispute disclosure duty that would have rendered the Owner's complaint not merely wrong but impossible to make in good faith.

The Board's conclusion that finding in the Owner's favor would have been unethical implicitly resolves a significant principle tension - between the faithful agent duty under Code Section II.4 and the objectivity obligation under Code Section II.3.a - without explicitly articulating the hierarchy between these duties. The more complete analytical extension is this: when an engineer is contractually designated as an impartial interpreter of contract documents, that designation does not eliminate the faithful agent relationship but rather redefines what faithful agency requires within that specific functional context. Faithful agency, properly understood, is not synonymous with advocacy or partisanship; it means acting in the Owner's genuine long-term interest, which includes the Owner's interest in having disputes resolved honestly and in accordance with the contract the Owner itself negotiated and signed. A finding in the Owner's favor unsupported by the evidence would have exposed the Owner to legal liability for wrongful rejection of conforming work, undermined the Owner's credibility in future disputes with the same or other contractors, and potentially constituted collusion against the Contractor - all outcomes contrary to the Owner's actual interests. Thus, the faithful agent duty and the impartiality obligation are not genuinely in conflict in this case; they converge on the same required conduct, and the Board's resolution of the apparent tension is correct but would benefit from this fuller articulation.

The Board's reliance on BER Case 85-5 to reinforce the objectivity principle, while analytically sound, raises a deeper question the Board did not address: whether Engineer A's prior involvement as designer - including his approval of the changes in the work that the Contractor relied upon - creates a structural confirmation bias risk that the objectivity principle itself should have required Engineer A to disclose or recuse himself from. When Engineer A ruled that the Contractor complied with the Owner-approved changes, he was simultaneously validating his own prior design-phase decisions. This is not merely an abstract conflict of interest; it is a situation where the engineer's impartial finding and his self-interest in vindicating his prior professional judgments point in the same direction. The Board's conclusion that Engineer A acted ethically is likely correct on the facts as presented, but a fully rigorous application of the objectivity obligation under Code Section II.3.a and the confirmation bias resistance principle drawn from BER 85-5 would require the Board to acknowledge that Engineer A's dual role as designer and dispute resolver creates a structural vulnerability to self-serving impartiality - that is, findings that are technically defensible but also conveniently consistent with the engineer's prior decisions. The ethical framework should therefore recognize that in cases where the dispute directly implicates the engineer's own prior design approvals, the engineer bears a heightened disclosure obligation, and the parties should be informed that a truly independent assessment might require a third-party reviewer.

The Owner's complaint that Engineer A owed a loyalty-based duty to find in the Owner's favor, while ethically mistaken, reveals a broader systemic problem that the Board's conclusion does not fully resolve: the standard construction contract architecture that designates the owner's own engineer as the impartial dispute resolver creates an inherent credibility deficit that neither party can fully escape. Even when the engineer rules correctly and impartially - as Engineer A did here - the structural appearance of partiality remains, because the engineer is simultaneously the Owner's retained professional and the purportedly neutral adjudicator. The Owner's complaint, however misguided in its specific claim, reflects a rational suspicion that an engineer retained and paid by the Owner cannot be genuinely impartial. Conversely, if Engineer A had ruled in the Owner's favor, the Contractor would have had equally rational grounds to question the impartiality of the finding. The Board's conclusion correctly resolves the specific ethical question presented, but the deeper analytical extension is that the NSPE Code and the profession more broadly should examine whether the standard AIA/EJCDC contract model - which assigns the owner's engineer this quasi-judicial role - is itself an ethically problematic structural arrangement that the profession should reform, rather than a practice whose ethical legitimacy can be fully secured through individual engineer conduct alone.

From a deontological perspective, the Owner's contractual agreement to Engineer A's impartial interpreter role generates not merely an estoppel against complaining about an adverse finding, but an affirmative ethical duty on the Owner's part not to demand that Engineer A violate the professional obligations the Owner helped establish. The Board's conclusion focuses on Engineer A's ethical duties but does not examine the reciprocal ethical obligations of the Owner as a party to a professional services relationship. Under the NSPE Code's framework of honesty and integrity, the Owner's complaint - demanding that Engineer A corrupt his professional judgment as a matter of loyalty - is itself ethically improper. It constitutes a request that Engineer A engage in the very conduct the Code prohibits: issuing a professional determination that is not objective and truthful. The Owner, having contractually designated Engineer A as impartial interpreter, cannot in good faith subsequently demand that Engineer A abandon that impartiality. This reciprocal ethical dimension - that clients bear duties not to demand that engineers violate their professional obligations - is an important analytical extension of the Board's conclusion that the profession should make more explicit, both to protect engineers from improper client pressure and to educate clients about the nature of the professional relationship they are entering.

In response to Q101: Engineer A did not bear a freestanding ethical duty to proactively warn the Owner, before accepting the dispute resolution role, that impartial findings might be adverse to the Owner's interests. The contractual provision designating Engineer A as initial interpreter and judge of work acceptability was itself the disclosure mechanism - it placed the Owner on constructive notice that Engineer A's determinations would follow the evidence rather than Owner preference. However, best practice would have supported an explicit pre-engagement conversation clarifying this role boundary, because such a conversation would have foreclosed the Owner's subsequent loyalty complaint at its inception. The absence of such a conversation did not render Engineer A's conduct unethical, but it did create the conditions for the Owner's misunderstanding. Had Engineer A provided explicit pre-dispute clarification, the ethical landscape would not have changed substantively - the impartiality obligation would have remained equally binding - but the Owner's complaint would have been even more clearly without foundation, and the professional relationship would have been better protected.

In response to Q102: The dual role of Engineer A - serving as both designer and construction-phase dispute resolver for the same Owner - does create a structural tension that warrants scrutiny, but it does not automatically constitute a disqualifying conflict of interest under the NSPE Code. The construction industry widely accepts the design engineer's role as initial interpreter of contract documents precisely because that engineer possesses the deepest knowledge of design intent. The structural tension becomes an actual conflict only when the engineer's prior design decisions are themselves the subject of the dispute, such that ruling in one direction would implicitly validate or repudiate the engineer's own prior work. In this case, the dispute concerned the Owner's approval of changes in the work and the Contractor's compliance with those changes - a factual determination that, while informed by design knowledge, did not require Engineer A to adjudicate the correctness of Engineer A's own original design choices. The credibility of Engineer A's impartiality is therefore not structurally undermined in this instance, though the dual-role arrangement should be recognized as one that demands heightened transparency and self-awareness from the engineer in every dispute it generates.

In response to Q103: If Engineer A had found in the Owner's favor on the same facts - facts that supported the Contractor's position - that finding would have constituted an ethical violation under NSPE Code Section II.3.a, which requires objectivity and truthfulness in professional determinations, and under Section III.1., which demands the highest standards of honesty and integrity. The standard the Board should apply to assess whether a dispute resolution finding was genuinely impartial versus subtly biased is a fact-grounded reasonableness standard: was the finding supported by the technical evidence available to the engineer at the time of review, and was the reasoning process free from the influence of the parties' interests? A finding that cannot be traced to articulable technical or contractual grounds, or that systematically diverges from the evidence in a direction that favors one party, should be treated as presumptively biased. In this case, Engineer A's finding that the Contractor complied with Owner-approved changes is a factually anchored conclusion, not a loyalty-driven one, and therefore satisfies the impartiality standard. A contrary finding, unsupported by the facts, would have been a form of professional dishonesty regardless of the loyalty rationale offered to justify it.

In response to Q104: The Owner's prior contractual agreement to Engineer A's role as impartial interpreter does create a form of estoppel that renders the Owner's loyalty complaint not merely factually mistaken but ethically problematic in its own right. By signing a contract that expressly designated Engineer A as the initial interpreter and judge of work acceptability, the Owner voluntarily accepted a framework in which Engineer A's findings would be governed by evidence and contractual requirements rather than by client preference. To subsequently demand that Engineer A override that framework in the Owner's favor is to ask Engineer A to breach both the contract and the professional ethics obligations the Owner was aware of when the engagement was established. This does not mean the Owner committed a formal ethical violation - the NSPE Code governs engineers, not clients - but it does mean the Owner's complaint lacks ethical legitimacy and should be understood as an attempt to retroactively redefine the terms of a professional relationship the Owner had already agreed to. The Board's implicit recognition of this dynamic reinforces the principle that contractual role clarity, once established, binds the expectations of all parties.

In response to Q201: The tension between the Faithful Agent Duty under NSPE Code Section II.4. and the Impartiality Obligation arising from Engineer A's contractual dispute resolution role is real but resolvable without abandoning either principle. The resolution lies in recognizing that the faithful agent duty is not equivalent to unconditional advocacy - it requires the engineer to act in the client's genuine interest, which includes performing contractually designated roles with integrity. When the Owner retained Engineer A under a contract that included an impartial interpreter provision, the Owner's genuine interest was served by having that provision performed honestly, because honest performance protects the Owner from contractor claims of bias, preserves the enforceability of dispute resolutions, and maintains the credibility of the entire construction administration process. The Impartiality Obligation therefore does not conflict with the Faithful Agent Duty in this context - it is the specific form the Faithful Agent Duty takes when the engineer's contractual role is quasi-judicial. The Impartiality Obligation takes precedence in the narrow sense that it defines the operative standard of conduct for this particular function, but it does so as an expression of, not a departure from, faithful agency.

In response to Q202: The Board's resolution - that impartiality is itself a form of loyalty when the engineer's contractual role is that of impartial arbiter - is analytically sound within the specific facts of this case, but it does carry a precedent risk that warrants acknowledgment. If the principle were applied without the limiting condition of a contractually established impartial role, it could be misused to justify engineer conduct adverse to clients in ordinary design or consulting contexts where no such role exists, on the theory that 'honest findings are always loyal.' That would be an overextension. The Board's reasoning is properly bounded by the contractual predicate: Engineer A's impartiality obligation arose from an explicit contract provision, not from a general claim that engineers owe impartiality to all parties in all circumstances. Future applications of this precedent should therefore be careful to distinguish cases where the engineer's impartial role is contractually established and mutually agreed upon from cases where an engineer unilaterally asserts impartiality as a shield against client service obligations. The ethical legitimacy of Engineer A's conduct rests on the contractual foundation, and that foundation must be present for the precedent to apply.

In response to Q203: The concern that Engineer A may have been validating his own prior design judgments rather than rendering a truly independent assessment is the most substantively challenging implicit question in this case. If the Owner's approval of changes in the work was itself a decision that Engineer A recommended or facilitated during the construction phase, then Engineer A's finding that the Contractor complied with those changes could reflect confirmation bias - a tendency to interpret ambiguous facts in a manner consistent with one's prior decisions - rather than genuine impartiality. The Objectivity Obligation under Section II.3.a. and the Confirmation Bias Resistance principle drawn from BER Case 85-5 together require that Engineer A's review be conducted as if the prior approvals were made by someone else, scrutinizing whether the Contractor's work actually conformed to the approved changes on their technical merits. The case record does not indicate that Engineer A's prior involvement in approving the changes was itself contested, which suggests the facts were sufficiently clear to support the finding without reliance on self-validating reasoning. However, this structural vulnerability - the designer-as-arbiter reviewing outcomes of the designer's own prior decisions - is a genuine limitation on the independence of the dispute resolution process that the parties and the profession should recognize when structuring construction administration contracts.

In response to Q204: The concern that repeated contractor-favorable rulings by a client-retained engineer could constitute disguised partiality is a legitimate systemic concern, but it does not apply to the facts of this case as presented, where a single finding is at issue. The Board should distinguish genuine impartiality from disguised partiality by applying a process-based standard rather than an outcome-based one: impartiality is demonstrated by the quality of the reasoning process - whether the engineer examined the evidence without predetermined conclusions, applied the contract documents consistently, and reached a finding that can be traced to articulable technical and contractual grounds - not by whether the finding favors one party or the other in any given instance. An engineer who consistently rules against the client is not necessarily biased toward the contractor; the engineer may simply be applying the contract correctly in cases where the contractor is consistently right. Conversely, an engineer who consistently rules for the client is not necessarily loyal in the proper sense - such a pattern would suggest the engineer is functioning as an advocate rather than an arbiter, which would itself be an ethical violation. The Collusion Avoidance obligation cuts in both directions: Engineer A must avoid both collusion with the Owner against the Contractor and the appearance of systematic bias toward the Contractor. A single finding, supported by the facts, satisfies neither concern.

In response to Q301: From a deontological perspective, Engineer A fulfilled the categorical duty of honesty and objectivity by ruling in the Contractor's favor when the facts supported that outcome. The NSPE Code's faithful agent obligation under Section II.4. does not impose a duty of unconditional advocacy; it imposes a duty of trustworthy service, which in the context of a contractually designated impartial role means performing that role with integrity. A deontological analysis grounded in Kantian ethics would hold that Engineer A's conduct is universalizable - if all engineers in impartial dispute resolution roles followed the evidence rather than client preference, the construction dispute resolution system would function with integrity and all parties would benefit from reliable, honest adjudication. The alternative - that engineers in impartial roles should favor their clients - is not universalizable, because it would render the impartial role meaningless and undermine the contractual framework that all parties, including owners, rely upon. The faithful agent obligation is therefore strictly bounded by the engineer's contractually designated role: within that role, faithful agency means honest performance, not partisan advocacy.

In response to Q302: From a consequentialist perspective, Engineer A's impartial ruling produced better long-term outcomes for all parties, including the Owner, than a loyalty-driven finding in the Owner's favor would have. Had Engineer A found in the Owner's favor despite the technical evidence supporting the Contractor, several adverse consequences would likely have followed: the Contractor would have had grounds to challenge the finding as biased, potentially escalating the dispute to formal arbitration or litigation at greater cost to all parties; the integrity of the construction administration process would have been compromised, exposing the Owner to future contractor claims of unfair dealing; Engineer A's professional credibility as a dispute resolver would have been undermined, reducing the value of the impartial interpreter provision in future disputes; and the Owner would have obtained a short-term win at the cost of a long-term weakening of the contractual dispute resolution framework that protects the Owner's interests throughout the construction project. The consequentialist calculus therefore strongly supports Engineer A's impartial conduct, and the Owner's complaint reflects a failure to appreciate the long-term consequences of the alternative the Owner was demanding.

In response to Q303: From a virtue ethics perspective, Engineer A demonstrated the professional virtues of integrity, courage, and practical wisdom by resisting the Owner's pressure and rendering an impartial finding. Integrity required Engineer A to align conduct with the contractual and professional obligations Engineer A had accepted; courage was required because finding against the client in a dispute the client expected to win carries professional and relational risk; and practical wisdom - phronesis - was demonstrated by Engineer A's recognition that genuine loyalty to the Owner's long-term interests required honest performance of the impartial role rather than short-term accommodation of the Owner's preference. The Owner's complaint itself reveals a misunderstanding of what virtuous professional loyalty requires. The Owner conflated loyalty with advocacy, treating Engineer A's role as equivalent to that of the Owner's legal counsel rather than that of a quasi-judicial arbiter. A virtuous professional does not abandon the integrity of a role simply because a client misunderstands what that role entails; rather, the virtuous professional performs the role with excellence and, where appropriate, educates the client about the nature of the obligations involved. Engineer A's conduct exemplifies this understanding of professional virtue.

In response to Q304: From a deontological perspective, the Owner's prior contractual agreement to Engineer A's impartial interpreter role does create a binding obligation on the Owner not to demand that Engineer A violate that role. This is not merely a contractual estoppel argument - it is an ethical one. If the Owner agreed to a contractual framework that designated Engineer A as an impartial arbiter, the Owner implicitly accepted the professional and ethical obligations that role entails, including the obligation that Engineer A's findings would be governed by evidence rather than loyalty. To subsequently demand that Engineer A breach those obligations is to ask Engineer A to act unethically, which is itself an ethically impermissible demand. The NSPE Code does not impose formal ethical duties on owners, but the ethical analysis of Engineer A's situation is clarified by recognizing that the Owner's complaint was not merely factually mistaken - it was a demand that Engineer A commit an ethical violation. Engineer A's refusal to comply with that demand was therefore not only ethically permissible but ethically required, and the Board's conclusion that finding in the Owner's favor would have been unethical directly supports this analysis.

In response to Q401: If Engineer A had found in the Owner's favor despite the technical evidence supporting the Contractor's position, Engineer A would have committed multiple ethical violations. Under Section II.3.a., Engineer A would have rendered a professional determination that was neither objective nor truthful, substituting client preference for evidence-based analysis. Under Section III.1., Engineer A would have acted contrary to the highest standards of honesty and integrity. Under Section III.3., Engineer A's finding could be characterized as a form of professional deception - presenting a biased determination as if it were an impartial one, thereby misleading the Contractor and potentially the public about the integrity of the dispute resolution process. Beyond ethical violations, such a finding would have exposed Engineer A to professional liability: the Contractor, having complied with Owner-approved changes, would have had grounds to challenge the finding as arbitrary and potentially to pursue claims against both the Owner and Engineer A for bad-faith dispute resolution. The integrity of the construction contract dispute resolution process would have been materially undermined, and Engineer A's conduct would have constituted a form of collusion with the Owner against the Contractor - precisely the outcome the Collusion Avoidance obligation is designed to prevent.

In response to Q402: If Engineer A had declined at the outset to serve as the impartial dispute resolver, citing the inherent tension between the loyal agent role and the quasi-judicial interpreter role, such a refusal would have been ethically defensible but not ethically required, and it is not clear that it would have better served the Owner's long-term interests. The construction industry's standard practice of designating the design engineer as initial interpreter of contract documents reflects a considered judgment that the designer's knowledge of design intent outweighs the structural tension created by the dual role, provided the engineer performs the role with integrity. A refusal to serve would have deprived the parties of the most knowledgeable arbiter available, potentially prolonged the dispute, and introduced the costs and delays associated with appointing a third-party arbitrator. However, if Engineer A had genuine reason to believe that the dual role would compromise the engineer's ability to render an impartial finding - for example, because the dispute directly implicated Engineer A's own prior design decisions in a way that created irresolvable bias - then declining the role would have been the more ethically cautious course. In the absence of such specific circumstances, Engineer A's decision to accept the role and perform it with integrity was the ethically appropriate choice.

In response to Q403: If BER Case 85-5 had not been available as analogical precedent, the ethical analysis of Engineer A's impartiality obligation would not have been materially weakened, because NSPE Code Section II.3.a. independently and directly compels the same conclusion. The requirement that engineers be objective and truthful in professional reports, statements, or testimony is a freestanding obligation that applies to all professional determinations, including dispute resolution findings. Engineer A's finding in the concrete pour dispute is a professional determination of the type Section II.3.a. governs, and the objectivity requirement admits of no exception for findings that happen to be adverse to the client. BER Case 85-5 strengthens the analysis by providing a cross-domain illustration of the objectivity principle - demonstrating that the Board has consistently applied this standard even when it produces results uncomfortable to the engineer's principal relationships - but the principle itself does not depend on the precedent. The Board's use of BER 85-5 is therefore best understood as confirmatory rather than foundational: it shows that the objectivity principle has been consistently applied, not that it requires analogical support to be operative.

In response to Q404: An Owner instruction, given prior to any dispute arising, that Engineer A's impartial interpreter role was subordinate to Engineer A's loyalty obligation would not have been enforceable as a matter of professional ethics, and compliance with such an instruction would not have been ethically permissible under the NSPE Code. The NSPE Code's ethical obligations - including the objectivity and truthfulness requirements of Section II.3.a. and the integrity standard of Section III.1. - are not contractually waivable by client instruction. An engineer cannot agree, in advance, to render biased professional determinations in exchange for client retention, because such an agreement would constitute a pre-commitment to dishonesty that violates the foundational ethical obligations of the profession. Furthermore, such an instruction would have effectively converted the impartial interpreter provision into a nullity, depriving the Contractor of the protection that provision was designed to afford. If the Owner had given such an instruction, Engineer A's ethically appropriate response would have been to decline to serve as the impartial interpreter under those conditions, or to clarify that the role could only be performed with integrity and that Engineer A would not agree in advance to findings that favor the Owner regardless of the evidence. The professional ethical duties of engineers set a floor that client instructions cannot lower.

The apparent conflict between the Faithful Agent Duty and the Impartiality Obligation is resolved in this case not by subordinating one to the other, but by recognizing that the contractually designated dispute resolution role redefines what faithful agency means in context. When an Owner retains an engineer to serve as the initial interpreter and judge of work acceptability, the Owner is contractually specifying the form that loyalty must take during disputes: impartial, fact-grounded adjudication. Engineer A's faithful agent duty was therefore not suspended during the dispute resolution phase - it was channeled through the impartiality obligation. The Board's conclusion that finding in the Owner's favor would have been unethical confirms that loyalty, in this structural context, is fulfilled by honest performance of the designated role, not by advocacy for the client's preferred outcome. This case teaches that the Faithful Agent Duty is not a fixed, content-invariant obligation but one whose specific demands are shaped by the contractual role the engineer has been assigned. Loyalty to an Owner who has contractually established an impartial arbiter role means honoring that role, not circumventing it.

The Objectivity Obligation and the Confirmation Bias Resistance principle interact in this case to impose a heightened standard of intellectual discipline on Engineer A precisely because his prior design decisions are implicated in the dispute. Because Engineer A had approved certain changes in the work that the Contractor relied upon, his dispute resolution finding was not rendered from a position of pure detachment - he was, in effect, evaluating the downstream consequences of his own earlier professional judgments. The Board's cross-application of BER Case 85-5, which condemned omission of ambiguous data to protect a preferred conclusion, signals that the objectivity obligation requires engineers to resist not only external pressure from clients but also internal cognitive pressure to validate prior decisions. This synthesis reveals a structural risk in dual-role arrangements: the engineer's impartiality may be compromised not by corruption or favoritism but by the natural human tendency to confirm one's own prior judgments. The ethical resolution in this case - that Engineer A's finding was proper - implicitly depends on the assumption that Engineer A successfully resisted this confirmation bias. The case therefore teaches that the Objectivity Obligation, when applied to a dispute resolver who is also the original designer, demands active self-scrutiny, not merely the absence of overt partiality.

The Owner Misapplication of Loyalty Principle and the Collusion Avoidance Through Impartial Performance principle together reveal that the Owner's complaint, while factually mistaken, also reflects a deeper conceptual error about the nature of professional loyalty in quasi-judicial engineering roles. The Owner's position - that loyalty required Engineer A to find in the Owner's favor - would, if accepted, transform the dispute resolution mechanism from an impartial adjudicative process into a pre-determined advocacy exercise. This would not merely harm the Contractor; it would undermine the very contractual architecture the Owner established and accepted. The principle of Collusion Avoidance Through Impartial Performance makes explicit what the Owner's complaint obscures: a loyalty-driven finding in the Owner's favor would have constituted a form of collusion against the Contractor, exposing Engineer A to professional and potentially legal liability. The case therefore teaches that the conventional understanding of client loyalty as advocacy is not merely insufficient in dispute resolution contexts - it is actively incompatible with the engineer's professional and contractual obligations. The Board's resolution of this tension establishes that when an engineer is contractually designated as an impartial arbiter, the Collusion Avoidance obligation and the Impartiality Obligation jointly override the advocacy dimension of client loyalty, and the Owner's contractual awareness of this structure estops the Owner from treating the resulting impartial finding as a breach of duty.

Did Engineer A owe an ethical duty to the Owner to find in the Owner's favor?

Did Engineer A have an obligation to proactively inform the Owner, before accepting the dispute resolution role, that his contractual duty of impartiality might produce findings adverse to the Owner's interests, and would such disclosure have altered the ethical landscape of this case?

Does the dual role of Engineer A - serving as both designer and construction-phase dispute resolver for the same Owner - create a structural conflict of interest that undermines the credibility of his impartiality, regardless of whether his technical finding was correct?

If Engineer A had found in the Owner's favor based on the same facts, would that finding have constituted an ethical violation, and what standard of review should the Board apply to assess whether a dispute resolution finding was genuinely impartial versus subtly biased?

Does the Owner's contractual awareness of Engineer A's impartiality role, combined with the Owner's subsequent acceptance of the ruling, create a form of estoppel that renders the Owner's loyalty complaint not merely factually wrong but ethically improper in itself?

Does the principle of Faithful Agent Duty - which obligates Engineer A to act in the Owner's interest - fundamentally conflict with the Impartiality Obligation that Engineer A's contractual dispute resolution role imposes, and if so, which principle takes precedence and on what ethical basis?

Is there a genuine tension between Loyalty Fulfilled Through Impartial Role Performance and the conventional understanding of client loyalty as advocacy, and does the Board's resolution of this tension - that impartiality is itself a form of loyalty - risk setting a precedent that could be misused to justify engineer conduct that is adverse to clients in contexts where no impartial-arbiter role was contractually established?

Does the Objectivity Obligation - requiring Engineer A to be truthful and unbiased in professional determinations - conflict with the Confirmation Bias Resistance principle when the engineer's prior design decisions are themselves implicated in the dispute, since Engineer A's approval of changes in the work that the Contractor relied upon may mean Engineer A is effectively validating his own prior judgments rather than rendering a truly independent assessment?

Does the principle of Collusion Avoidance Through Impartial Performance conflict with the Faithful Agent Obligation when the engineer's impartial finding consistently favors one party - the Contractor - since repeated contractor-favorable rulings by a client-retained engineer could raise questions about whether the engineer's 'impartiality' is itself a form of misaligned loyalty, and how should the Board distinguish genuine impartiality from disguised partiality in either direction?

From a deontological perspective, did Engineer A fulfill their categorical duty of honesty and objectivity by ruling in the Contractor's favor, even though this conflicted with the Owner's expectation of loyalty, and does the NSPE Code's faithful agent obligation impose a duty that is strictly bounded by the engineer's contractually designated impartial role?

From a consequentialist perspective, did Engineer A's impartial ruling produce better long-term outcomes for all parties - including the Owner - than a loyalty-driven finding in the Owner's favor would have, particularly with respect to the integrity of the construction process, future dispute resolution credibility, and avoidance of collusion?

From a virtue ethics perspective, did Engineer A demonstrate the professional virtues of integrity, courage, and impartiality by resisting the Owner's pressure to find in their favor, and does the Owner's complaint itself reveal a misunderstanding of what virtuous professional loyalty actually requires of an engineer serving in a quasi-judicial dispute resolution role?

From a deontological perspective, does the Owner's prior contractual agreement to Engineer A's role as impartial interpreter create a binding estoppel that makes the Owner's subsequent loyalty complaint not merely factually mistaken but ethically impermissible - that is, does the Owner have a duty not to demand that Engineer A violate the very contractual and professional obligations the Owner helped establish?

If Engineer A had found in the Owner's favor despite the technical evidence supporting the Contractor's position, what ethical violations would Engineer A have committed, and would such a finding have exposed Engineer A to professional liability, undermined the integrity of the construction contract dispute resolution process, or constituted collusion with the Owner against the Contractor?

What if Engineer A had declined to serve as the impartial dispute resolver at the outset, citing the inherent tension between the loyal agent role and the quasi-judicial interpreter role - would such a refusal have been ethically preferable, and would it have better served the Owner's long-term interests by prompting appointment of a truly independent third-party arbitrator?

If the BER Case 85-5 precedent regarding omission of ambiguous data had not been available to the Board, would the ethical analysis of Engineer A's impartiality obligation have been materially weakened, or does the objectivity principle embedded in NSPE Code Section II.3.a independently compel the same conclusion regardless of analogical precedent?

What if the Owner had explicitly instructed Engineer A, prior to the dispute arising, that Engineer A's role as impartial interpreter was subordinate to Engineer A's loyalty obligation - would such an instruction have been enforceable, and would compliance with it have been ethically permissible under the NSPE Code, or would it have constituted an impermissible contractual override of Engineer A's professional ethical duties?

By accepting retention in both the design and construction phases while also serving as contractual dispute interpreter, Engineer A fulfills the faithful agent obligation but is immediately constrained by the requirement that this dual role not collapse into partisan loyalty - the contract provision for impartiality defines the outer boundary of what the retention can ethically entail.

Asserting impartiality over loyalty directly fulfills Engineer A's contractual and ethical obligation to resist the Owner's misapplication of the loyalty principle, and is guided by the principle that true loyalty to a client who knowingly signed an impartiality clause is best expressed through faithful, non-partisan role execution rather than partisan advocacy.

Conducting the impartial dispute review is the central action through which Engineer A operationalizes all objectivity and impartiality obligations, constrained by the BER 93-4 requirement that the review be fact-grounded and candid, and analogically informed by the BER 85-5 prohibition on confirmation bias and selective data omission in technical reporting.

Ruling in the Contractor's favor is the concrete outcome of impartial, fact-grounded review and fulfills Engineer A's objectivity and impartiality obligations precisely because it reflects the technical merits rather than client loyalty, with the constraint that the ruling must be defensible on factual grounds alone to avoid any appearance of collusion or confirmation bias.

This question emerged because the Owner's complaint reframed a contractually mandated impartial ruling as a breach of loyalty, forcing the Board to adjudicate whether the faithful-agent duty is overridden or fulfilled by role-faithful impartial performance. The collision between the Owner's intuitive expectation of client-side advocacy and the contract's explicit neutrality obligation created the ethical ambiguity the question addresses.

This question arose because the case record is silent on whether Engineer A explicitly counseled the Owner about the risk of an adverse finding before assuming the dispute resolver role, leaving open whether the ethical duty of candor required more than contractual boilerplate. The absence of documented pre-role disclosure created a structural gap that the question probes - asking whether silence at role-acceptance constitutes an ethical omission independent of the subsequent ruling's correctness.

This question emerged because the same facts that establish Engineer A's contractual authority to resolve the dispute also establish his pre-existing loyalty relationship with one of the disputing parties, creating an irreducible structural tension that the question forces the Board to evaluate independently of outcome correctness. The Owner's complaint, paradoxically, surfaced this structural issue by alleging bias in the direction opposite to what the structural conflict would predict, making the credibility of impartiality - not just its exercise - a live ethical question.

This question emerged as a logical stress-test of the Board's impartiality framework: if the ruling's ethical validity is independent of its direction, the Board must articulate what standard distinguishes genuine impartiality from sophisticated bias, since a biased engineer could always claim objectivity. The cross-application of BER 85-5's confirmation-bias analysis sharpens the question by providing a precedent framework for detecting motivated technical conclusions, forcing the Board to specify whether that framework applies to dispute resolution findings.

This question emerged because the Owner's sequential conduct - consent, acceptance, then complaint - created a temporal inconsistency that raises the question of whether the ethics complaint itself constitutes a misuse of the professional accountability system. The estoppel framing transforms the question from 'did Engineer A act ethically?' to 'is the Owner's complaint itself an ethical violation?', a second-order question that the case's procedural posture uniquely generates.

This question emerged because Engineer A's dual-role structure placed two professionally authoritative warrants in direct opposition at the moment of adjudication: the general agency relationship with the Owner activated the loyalty warrant, while the specific contractual dispute-resolution clause activated the impartiality warrant. The Owner's post-ruling criticism made the precedence question unavoidable, since accepting either warrant as supreme without principled justification would leave the other systematically violated.

This question arose because the Board's resolution of the loyalty-impartiality conflict, while internally coherent for the BER 93-4 facts, produced a novel and potentially expansive reinterpretation of client loyalty that the question tests for precedential stability. The data of Engineer A ruling against the Owner while claiming to act loyally exposed the gap between the conventional and the Board's reconstructed meaning of loyalty, making it necessary to examine whether the resolution is principled or merely situationally convenient.

This question emerged because the cross-application of BER 85-5's confirmation bias principle to the dispute-resolution context exposed a structural vulnerability in Engineer A's position: the same facts that establish Engineer A's technical competence to adjudicate the dispute (prior design and construction-phase involvement) also establish the conditions under which confirmation bias is most likely to operate. The question arose because the Board's invocation of objectivity did not explicitly address whether Engineer A's prior role contaminated the independence that objectivity requires.

This question arose because the structural asymmetry of the engineer-client relationship means that any contractor-favorable ruling carries an inherent appearance problem that a single ruling cannot fully resolve: the data of repeated adverse findings against the retaining party creates a pattern that the impartiality warrant alone cannot neutralize without an independent verification mechanism. The question exposes the Board's failure to specify how genuine impartiality is distinguished from its disguised inverse when the observable outputs are identical.

This question emerged because the deontological framing forces a precision that the Board's pragmatic resolution does not fully supply: whether the faithful agent obligation is categorically bounded by the contractual impartial-arbiter role or whether it persists as a competing categorical duty that the engineer must consciously override. The Owner's criticism made the deontological stakes explicit - Engineer A's ruling was experienced as a breach of duty - requiring analysis of whether the NSPE Code's faithful agent provision is strictly bounded by role designation or whether it imposes residual obligations that survive role-specific contractual constraints.

This question emerged because the data - an impartial ruling against the Owner followed by the Owner's complaint - creates a genuine consequentialist contest: did fidelity to the quasi-judicial role actually produce better outcomes than a loyalty-driven finding would have? The question forces evaluation of whether the two warrants (impartiality and client benefit) converge or diverge in their long-term consequences.

This question arose because the Owner's complaint - itself a data event - implicitly invokes a conception of professional loyalty as partisan advocacy, which directly contests the virtue ethics framework under which Engineer A's impartiality constitutes integrity and courage rather than disloyalty. The question emerges from the collision between two competing accounts of what virtuous professional conduct requires in a dual-role context.

This question emerged because the data reveals a structural paradox: the Owner simultaneously created the impartiality obligation through contract and then complained that Engineer A honored it, generating a deontological question about whether the Owner's complaint is itself an ethical violation. The estoppel warrant and the loyalty warrant cannot both apply, and the question forces resolution of which duty takes precedence when the Owner is both the source and the challenger of the impartiality obligation.

This counterfactual question emerged because the actual data - Engineer A ruling for the Contractor against Owner pressure - invites examination of the ethical stakes of the road not taken, specifically whether a loyalty-driven ruling would have crossed from permissible discretion into actionable ethical violation. The question arises from the tension between the loyalty warrant the Owner implicitly invoked and the cluster of professional integrity, objectivity, and collusion-avoidance warrants that would have been violated by compliance.

This question emerged because the data - specifically the act of accepting dual-role retention followed by the downstream loyalty complaint - reveals that the structural tension between loyal agent and impartial interpreter was latent from the beginning of the engagement, raising the question of whether the ethical problem could and should have been avoided upstream. The competing warrants on role-conflict disclosure versus dual-role acceptance create genuine uncertainty about whether Engineer A's ethical obligations were best discharged at the point of retention rather than at the point of dispute resolution.

This question arose because the Board's reasoning visibly relied on BER 85-5 as analogical support, making it structurally ambiguous whether the ethical conclusion about Engineer A's impartiality was jointly produced by precedent plus Code principle or whether the Code principle alone was sufficient - a distinction that matters for the precedential weight and generalizability of the ruling. The question forces explicit examination of whether analogical precedent is constitutive of or merely corroborative of the ethical obligation, exposing a latent dependency in the argument's warrant structure.

This question arose because the Owner's post-hoc loyalty complaint implicitly raised the prior question of whether such a loyalty-priority instruction could have been legitimately issued before the dispute, exposing the unresolved tension between the engineer's status as a faithful agent of the client and the engineer's status as a professionally and contractually constrained impartial adjudicator whose role integrity cannot be privately bargained away by one party. The question crystallizes the structural limit of the faithful-agent warrant: it authorizes client direction only up to the boundary where professional ethical obligations and third-party contractual reliance interests begin.

The Board concluded that finding in the Owner's favor would have been unethical because the faithful agent duty and the impartiality obligation are not genuinely in conflict; rather, they converge on the same required conduct when the engineer's contractual role as impartial interpreter is properly understood as itself an expression of what the Owner's long-term interests actually require.

The Board concluded directly and without qualification that it would have been unethical for Engineer A to find in the Owner's favor contrary to his considered professional findings, establishing the core holding that professional objectivity is not subordinate to client loyalty in the context of a contractually designated dispute resolution role.

The Board's conclusion that Engineer A acted ethically is affirmed but found incomplete, because a fully rigorous analysis would require examining whether Engineer A discharged a pre-dispute disclosure duty to inform the Owner that the impartial-interpreter role could produce findings adverse to the Owner's interests - a duty whose fulfillment would have resolved the informational asymmetry underlying the Owner's complaint.

The Board's conclusion that Engineer A acted ethically is likely correct on the facts presented, but a fully rigorous application of the objectivity obligation and confirmation bias resistance principle would require acknowledging that Engineer A's dual role as designer and dispute resolver creates a structural vulnerability to self-serving impartiality, imposing a heightened disclosure obligation and potentially warranting recommendation of a third-party reviewer when the dispute directly implicates the engineer's own prior design approvals.

The Board correctly resolved the specific ethical question by finding that Engineer A acted ethically, but the deeper analytical extension is that the standard AIA/EJCDC contract model - which assigns the owner's engineer a quasi-judicial dispute resolution role - is itself a structurally ethically problematic arrangement that the profession should examine and potentially reform, because the appearance of partiality it creates cannot be fully eliminated through individual engineer conduct alone, regardless of how correctly and impartially the engineer performs.

The board concluded that the Owner's complaint was not merely factually mistaken but ethically improper in its own right, because the Owner had voluntarily established the framework of impartiality and could not in good faith subsequently demand its abandonment; this reciprocal ethical dimension - that clients bear duties not to demand engineers violate professional obligations the clients helped create - was identified as an analytical extension the profession should make more explicit.

The board concluded that Engineer A bore no freestanding ethical duty to proactively warn the Owner before accepting the dispute resolution role, because the contractual designation itself served as the disclosure mechanism; however, the board noted that an explicit pre-dispute clarification conversation, while not ethically required, would have been best practice and would have rendered the Owner's subsequent loyalty complaint even more clearly without foundation.

The board concluded that Engineer A's dual role did not constitute a disqualifying conflict of interest in this instance because the dispute was a factual determination about compliance with Owner-approved changes rather than a judgment about the correctness of Engineer A's original design, while cautioning that the dual-role arrangement demands heightened transparency and self-awareness in every dispute it generates.

The board concluded that a finding in the Owner's favor on the same facts would have constituted an ethical violation under Sections II.3.a and III.1, and articulated a fact-grounded reasonableness standard for assessing impartiality - requiring that findings be traceable to articulable technical or contractual grounds and free from party-interest influence - which Engineer A's actual finding satisfied and a contrary finding would not have.

The board concluded that the Owner's contractual awareness of and agreement to Engineer A's impartial role created a form of estoppel rendering the loyalty complaint not merely factually mistaken but ethically improper, because the Owner voluntarily entered a professional relationship governed by evidence-based determination and could not legitimately demand its corruption after receiving an adverse finding.

The board concluded that no true conflict exists between the Faithful Agent Duty and the Impartiality Obligation because the Owner's genuine interest was served by honest performance of the impartial role; the Impartiality Obligation was held to be the specific expression of faithful agency within the contractually designated quasi-judicial function, not a departure from it.

The board affirmed its resolution that impartiality is a form of loyalty in this case but acknowledged a genuine precedent risk, resolving it by articulating a clear limiting condition - the principle applies only where the engineer's impartial role is contractually established, not where an engineer unilaterally asserts impartiality as a shield against ordinary client service obligations.

The board concluded that while the designer-as-arbiter role creates a genuine structural vulnerability to confirmation bias, the case record did not indicate that Engineer A's prior involvement was contested or that self-validating reasoning was employed, making the finding defensible under the Objectivity Obligation - though the board explicitly flagged this dual-role structure as a limitation the profession should address in contract design.

The board concluded that the concern about disguised partiality through repeated contractor-favorable rulings does not apply to a single, evidence-supported finding, and established that genuine impartiality must be evaluated by whether the engineer examined evidence without predetermined conclusions and applied contract documents consistently, not by whether the outcome favored the client or the contractor.

The board concluded from a deontological perspective that Engineer A fulfilled the categorical duty of honesty and objectivity by following the evidence, and that the NSPE Code's faithful agent obligation does not impose unconditional advocacy but rather trustworthy service within the engineer's designated role - a standard that, when universalized, produces a construction dispute resolution system of integrity that benefits all parties including owners.

The board concluded that Engineer A's impartial ruling produced superior outcomes for all parties, including the Owner, because a loyalty-driven finding would have triggered contractor challenges, escalated costs, compromised the dispute resolution framework, and undermined Engineer A's credibility - all of which would have harmed the Owner more than the adverse ruling did. The Owner's complaint was therefore not only ethically misguided but strategically self-defeating.

The board concluded that Engineer A exemplified the professional virtues of integrity, courage, and practical wisdom by refusing to capitulate to Owner pressure, and further concluded that the Owner's complaint revealed a category error - mistaking the quasi-judicial arbiter role for an advocacy role - which a virtuous professional is obligated to resist and, where appropriate, correct through client education rather than compliance.

The board concluded that the Owner's prior agreement to Engineer A's impartial interpreter role created a binding ethical obligation on the Owner not to demand that Engineer A violate that role, because the Owner had implicitly accepted that Engineer A's findings would be evidence-governed rather than loyalty-governed, and demanding otherwise was itself an ethically impermissible act - not merely a factual misunderstanding.

The board concluded that a finding in the Owner's favor despite contrary technical evidence would have violated Section II.3.a. (objectivity and truthfulness), Section III.1. (honesty and integrity), and Section III.3. (deception of the public), and would additionally have constituted collusion with the Owner against the Contractor - exposing Engineer A to professional liability and materially undermining the integrity of the construction contract dispute resolution process.

The board concluded that Engineer A's decision to accept the impartial interpreter role and perform it with integrity was ethically appropriate because the industry's standard practice reflects a considered judgment that design knowledge outweighs structural role tension, and because no specific circumstances existed in this case that would have made the dual role irresolvably biased - meaning refusal, while defensible, was not required and would not have better served the Owner's long-term interests.

The board concluded that the ethical analysis would not have been materially weakened without BER Case 85-5 because Section II.3.a.'s objectivity and truthfulness requirement independently and directly compels impartiality in all professional determinations, including dispute resolution findings; BER Case 85-5 was used only to demonstrate consistent historical application of a principle that stands on its own textual and normative footing.

The board concluded that a pre-dispute Owner instruction subordinating Engineer A's impartiality to loyalty would have been unenforceable and ethically impermissible because such an instruction would constitute a pre-commitment to dishonesty in violation of Sections II.3.a. and III.1., and Engineer A's appropriate response would have been to decline the impartial interpreter role or to clarify that the role could only be performed with integrity intact.

The board concluded that no genuine subordination of one duty to the other was required because the Owner's own contractual designation of Engineer A as impartial arbiter redefined what faithful agency demanded in the dispute resolution context, such that loyalty was fulfilled - not violated - by rendering an honest, evidence-grounded finding adverse to the Owner's preferred outcome.

The board concluded that Engineer A's dual role as designer and dispute resolver created a structural confirmation bias risk that the Objectivity Obligation required him to actively counteract, and that the ethical validity of his finding depended not only on the absence of external favoritism but on genuine resistance to the internal cognitive tendency to validate his own prior professional judgments, as cross-illuminated by the omission-of-ambiguous-data standard from BER Case 85-5.

The board concluded that the Owner's complaint reflected not merely a factual misunderstanding of Engineer A's role but a deeper conceptual error about the nature of professional loyalty in quasi-judicial engineering contexts, and that the Owner's prior contractual establishment of the impartial interpreter provision created an estoppel that rendered the loyalty complaint ethically impermissible - because accepting it would have required Engineer A to collude against the Contractor in violation of the very contractual architecture the Owner had designed and accepted.

Should Engineer A render an impartial, evidence-based determination in the Owner-Contractor concrete pour dispute even though it finds against the Owner, or should Engineer A find in the Owner's favor on loyalty grounds?

Should Engineer A maintain the impartial determination adverse to the Owner and correct the Owner's misapplication of the loyalty principle, or acquiesce to the Owner's pressure and revise the finding in the Owner's favor?

Should Engineer A proactively disclose the role-inherent tension between loyal agency and contractual impartiality - and the structural confirmation bias risk arising from the dual designer-arbiter role - before accepting the dispute resolution function, or rely on the contractual impartiality clause as sufficient constructive notice?

Should Engineer A base the concrete pour determination strictly on the established facts of Owner approval and Contractor compliance, or should Engineer A conduct a broader technical re-examination that actively seeks out and engages with data at variance with the Contractor-favorable conclusion?

Should the Owner accept Engineer A's impartial adverse finding as the legitimate product of the contractual framework the Owner established and signed, or press the loyalty-based complaint demanding that Engineer A revise the finding in the Owner's favor?