Step 4: Full View

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

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

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.

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.

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.

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

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

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.

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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

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.

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

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.

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.