Step 4: Full View
Entities, provisions, decisions, and narrative
Full Entity Graph
Loading...Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chainThe board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.
NSPE Code Provisions Referenced
Section I. Fundamental Canons 2 48 entities
Hold paramount the safety, health, and welfare of the public.
Act for each employer or client as faithful agents or trustees.
Section II. Rules of Practice 3 94 entities
Engineers shall not falsify their qualifications or permit misrepresentation of their or their associates' qualifications. They shall not misrepresent or exaggerate their responsibility in or for the subject matter of prior assignments. Brochures or other presentations incident to the solicitation of employment shall not misrepresent pertinent facts concerning employers, employees, associates, joint venturers, or past accomplishments.
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 avoid deceptive acts.
Section III. Professional Obligations 3 100 entities
Engineers shall not attempt to obtain employment or advancement or professional engagements by untruthfully criticizing other engineers, or by other improper or questionable methods.
Engineers shall be guided in all their relations by the highest standards of honesty and integrity.
Engineers shall avoid the use of statements containing a material misrepresentation of fact or omitting a material fact.
Cross-Case Connections
View ExtractionExplicit Board-Cited Precedents 2 Lineage Graph
Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.
Principle Established:
An engineer is not automatically compelled to disclose a pending ethics complaint to a client, as a complaint is a mere allegation and not a finding of fact; however, the engineer should weigh providing limited background information to the client in a dispassionate manner.
Citation Context:
The Board cited this case to establish the baseline obligation of disclosure to clients regarding pending ethics complaints, then distinguished it from the present case because Engineer F's contractor license revocation was an actual adjudication of wrongdoing rather than a mere allegation.
Principle Established:
Personal misconduct not directly related to the practice of engineering is still subject to the NSPE Code of Ethics, because the purpose of a code of ethics is to ensure the public can have confidence in the integrity, honesty, and decorous behavior of professional practitioners.
Citation Context:
The Board cited this case to support the principle that personal misconduct unrelated to the direct practice of engineering can still constitute a violation of the NSPE Code of Ethics, broadening the ethical analysis beyond Engineer F's engineering license to his contractor license revocation.
Implicit Similar Cases 10 Similarity Network
Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.
Questions & Conclusions
View ExtractionDid Engineer F have an ethical obligation to report on the employment application the revocation of his contractor’s license?
Engineer F had an ethical obligation to report on the employment application the revocation of his contractor’s license.
Does the ethical obligation to disclose the contractor license revocation change depending on whether the employment application question was drafted narrowly by the hiring firm, and does the firm's imprecise drafting bear any moral weight in distributing responsibility for the omission?
The narrow wording of the employment application question does not meaningfully redistribute moral responsibility for Engineer F's omission to the hiring firm. While the engineering firm could have drafted a more comprehensive disciplinary inquiry question, the ethical obligation to disclose material integrity information flows from Engineer F's own duties under the NSPE Code - not from the precision of the questioner's drafting. An engineer who exploits an imprecisely worded question to omit an adjudicated integrity violation is not acting as a faithful agent or trustee; he is engaging in legalistic self-protection that the Code explicitly prohibits. The firm's imperfect drafting may reflect a due diligence gap on its part, but it does not constitute a moral license for Engineer F to withhold information that any reasonable employer would consider material to a hiring decision. The ethical obligation to avoid deceptive acts and technically misleading statements is self-executing - it does not depend on the sophistication of the question posed.
The Allegation-Adjudication Distinction - used to differentiate Engineer F's case from BER Case 97-11, where Engineer A faced only a pending ethics complaint - resolves a latent tension between the Prudential Disclosure principle and the Omission Materiality principle by establishing a graduated disclosure threshold rather than a binary rule. Under BER 97-11, the Board declined to impose a categorical obligation on Engineer A to disclose a mere allegation, recognizing that unresolved complaints carry uncertain probative weight and that premature disclosure could itself be misleading or unfair. In Engineer F's case, however, the contractor license revocation is an adjudicated finding: a formal governmental determination that Engineer F committed a specific integrity violation. The synthesis of these two cases teaches that the disclosure obligation is calibrated to epistemic certainty and adjudicative finality: allegations occupy a zone of prudential weighing where disclosure may be advisable but is not categorically required, while adjudicated findings of wrongdoing - particularly those involving integrity violations in safety-sensitive domains - cross a threshold of materiality that makes non-disclosure on a professional employment application an ethics violation. The principle hierarchy is therefore: Omission Materiality (adjudicated findings) > Prudential Disclosure (allegations), with the Allegation-Adjudication Distinction serving as the operative boundary between the two regimes. This also implies that the moral responsibility for the informational gap created by the firm's narrow application drafting diminishes as the certainty and severity of the undisclosed finding increases - Engineer F cannot shift responsibility to the firm's imprecise drafting when the omitted fact is an adjudicated revocation for an integrity violation.
Beyond the initial employment application, did Engineer F acquire a continuing or renewed ethical obligation to disclose the contractor license revocation to his employer once he was hired, and if so, at what point does that obligation arise?
The Board's reasoning, read in light of its comparative analysis distinguishing BER Case 97-11, establishes a meaningful threshold: an adjudicated finding of wrongdoing - as opposed to a pending allegation or unresolved complaint - triggers a firm disclosure obligation on a professional employment application even when the disciplinary action arose outside the PE license domain. This allegation-adjudication distinction is not merely procedural; it reflects the epistemic difference between an unproven claim and a formally determined fact about the applicant's character. Because Engineer F's contractor license revocation was a completed adjudication, he could not invoke the uncertainty or reputational-harm rationale that might counsel caution about disclosing unresolved allegations. Furthermore, the Board's reasoning implies a continuing obligation: once hired, Engineer F's duty as a faithful agent and trustee to his employer would independently require disclosure of the revocation, since concealing a material adjudicated integrity finding from an employer who would reasonably consider it relevant to the employment relationship is inconsistent with the faithful agency canon. The ethical obligation thus did not expire at the moment of hiring but persisted as a relational duty throughout the employment relationship.
Engineer F's ethical obligation to disclose the contractor license revocation did not terminate upon submission of the employment application. Once hired, Engineer F entered into a fiduciary-adjacent relationship with his employer as a faithful agent and trustee under the NSPE Code. That relationship independently activates a continuing duty of candor regarding material facts bearing on his fitness and integrity. The moment Engineer F became aware that his employer was operating under a materially incomplete understanding of his professional history - an understanding Engineer F himself had created through omission - a renewed and arguably stronger disclosure obligation arose. This obligation would crystallize at the latest when the employer's reliance on the incomplete record became consequential, such as when Engineer F was assigned to projects, given supervisory authority, or held out to clients as a qualified professional. Silence in the face of a known material omission, once an employment relationship has been established, compounds rather than cures the original ethical breach.
Would Engineer F's ethical disclosure obligation differ if the contractor license revocation had been for a purely administrative or technical violation unrelated to integrity - such as a paperwork lapse - rather than for allowing an unlicensed individual to misuse his license number?
Engineer F's disclosure obligation would be materially weaker if the contractor license revocation had arisen from a purely administrative or technical violation - such as a paperwork lapse or failure to renew on time - rather than from the integrity-implicating conduct of allowing an unlicensed individual unrelated to his firm to use his contractor license number. The ethical weight of a disclosure obligation scales with the character relevance of the underlying conduct. Administrative failures speak primarily to organizational competence; they do not necessarily implicate the honesty, trustworthiness, or professional integrity that the NSPE Code's whole-person character standard is designed to assess. By contrast, deliberately lending a license number to an unrelated unlicensed individual is an affirmative act of deception that undermines the very licensing system designed to protect the public - conduct that sits at the core of what the Code's integrity provisions address. The adjudicated nature of the revocation matters, but so does the moral character of the underlying act. A purely technical revocation might fall below the materiality threshold for mandatory disclosure on a PE employment application; the actual conduct here clearly does not.
Does the fact that Engineer F's misconduct - lending his contractor license number to an unrelated unlicensed individual - directly implicates the same professional integrity norms that govern PE licensure create a heightened disclosure obligation compared to a contractor license revocation arising from entirely unrelated conduct?
The Board's conclusion that Engineer F had an ethical obligation to disclose the contractor license revocation rests not merely on the fact of revocation but on the nature of the underlying conduct: deliberately allowing an unlicensed individual unrelated to his firm to use his contractor license number. This act directly implicates the same professional integrity norms - honesty, faithful agency, and protection of the public - that govern PE licensure. Because the misconduct was not a technical or administrative lapse but an affirmative integrity violation adjudicated through a formal proceeding, the ethical obligation to disclose was heightened beyond what would apply to a purely procedural license deficiency. The safety-critical domain of fire sprinkler contracting further amplifies this materiality, since the public safety stakes of that field mirror those that animate engineering ethics codes generally. Accordingly, Engineer F's disclosure obligation was not merely triggered by the existence of a revocation but was intensified by the character of the conduct that produced it.
The fact that Engineer F's misconduct - lending his contractor license number to an unrelated unlicensed individual - directly implicates the same professional integrity norms that govern PE licensure creates a heightened, not merely equivalent, disclosure obligation. Licensing systems across engineering and contracting domains share a common foundational purpose: ensuring that only qualified, accountable individuals perform work that affects public safety. When an engineer subverts that system in one licensed domain by enabling unlicensed practice, the conduct speaks directly to his fitness to be trusted with the responsibilities of PE licensure in another. The fire protection context amplifies this further: fire sprinkler systems are life-safety infrastructure, and allowing an unlicensed individual to operate under a contractor license number in that domain is not a technical irregularity but a public safety violation. The cross-domain integrity relevance and the safety-critical nature of the field together elevate the materiality of the revocation well beyond what would apply to a license revocation in an unrelated, non-safety-sensitive domain.
Does the principle that engineers are entitled to rely on the literal scope of a question asked of them - Employment Application Question Scope Fidelity - conflict with the principle that technically true but misleading answers are ethically prohibited, and how should an engineer resolve that tension when the question's wording is narrower than its evident purpose?
The Board's conclusion implicitly rejects the argument that Engineer F could ethically rely on the narrow literal wording of the employment application question - which referenced only discipline 'in the practice of professional engineering' - to justify omitting the contractor license revocation. Under the NSPE Code's prohibition on deceptive acts and its requirement that engineers avoid statements containing material omissions that create false impressions, a technically accurate answer that is crafted to exploit a question's imprecise drafting is ethically equivalent to a misrepresentation when the omitted information is material to the purpose the question was plainly designed to serve. The evident purpose of the disciplinary question was to assess the applicant's character and fitness for professional trust, not merely to audit PE license status in a narrow administrative sense. Engineer F's exploitation of the question's literal scope to conceal an adjudicated integrity violation therefore constitutes the kind of artfully misleading omission the Code prohibits, regardless of whether his PE license itself was ever disciplined. The firm's failure to draft a more comprehensive question does not transfer moral responsibility for the omission to the firm; the duty of candor rests with the applicant.
The tension between Employment Application Question Scope Fidelity - the notion that an engineer may answer only what is literally asked - and the prohibition on technically true but misleading statements is resolved decisively in favor of the latter under the NSPE Code. The Code does not permit an engineer to treat a questioner's imprecise drafting as a loophole through which material integrity information may be withheld. The evident purpose of the employment application's disciplinary question was to assess whether the applicant had a history of adjudicated professional misconduct bearing on his fitness for a PE role. Engineer F's answer was technically accurate in its narrowest reading but functionally deceptive in its effect: it conveyed to the hiring firm that no relevant disciplinary history existed, when in fact an adjudicated revocation for an integrity violation in a safety-critical licensed domain did exist. The Code's provisions on deceptive acts and material omissions are not satisfied by literal accuracy alone; they require that the overall impression conveyed be truthful. Engineer F's answer failed that standard.
The tension between Employment Application Question Scope Fidelity - the idea that an applicant may legitimately confine answers to the literal scope of a question - and the Technically True But Misleading Statement Prohibition was resolved decisively in favor of the latter. The Board implicitly held that when a question's evident purpose is to assess character and fitness for professional trust, an engineer cannot exploit narrow drafting to suppress a material adjudicated integrity violation. The narrow wording of the application question ('disciplined in the practice of professional engineering or had his license suspended or revoked') did not exculpate Engineer F because the ethics code imposes a duty to interpret such questions according to their evident purpose rather than their most self-serving literal reading. This resolution teaches that Question Scope Fidelity is a subordinate principle: it governs genuinely ambiguous or irrelevant omissions, but it yields entirely when the omitted information is both material to the questioner's evident purpose and reflects an adjudicated finding of wrongdoing by the applicant. The principle hierarchy is therefore: Technically True But Misleading Statement Prohibition > Employment Application Question Scope Fidelity, whenever the gap between literal scope and evident purpose is exploited to conceal integrity-relevant conduct.
How should the Whole-Person Character Integrity Standard - which extends ethical scrutiny to non-engineering conduct - be reconciled with the principle that the ethics code's jurisdiction is ordinarily bounded by professional engineering practice, given that Engineer F's contractor license revocation arose outside his PE role?
The Whole-Person Character Integrity Standard drawn from BER Case 75-5 can be reconciled with the ordinary jurisdictional boundaries of the engineering ethics code by recognizing that the Code's reach is not defined by the domain in which conduct occurs, but by whether the conduct is relevant to the engineer's fitness to fulfill professional engineering obligations. The Code does not claim jurisdiction over every aspect of an engineer's personal life; it does claim jurisdiction over conduct that bears on honesty, integrity, and public safety - wherever that conduct occurs. Engineer F's contractor license revocation arose outside his PE role but directly implicated the same integrity norms - prohibition on enabling unlicensed practice, protection of licensing system integrity, and public safety - that the PE ethics code enforces. The cross-domain character relevance, not the domain of occurrence, is the operative jurisdictional trigger. This reading avoids both over-extension of the Code into genuinely private conduct and under-extension that would allow engineers to compartmentalize integrity violations by domain.
The Whole-Person Character Integrity Standard - drawn from BER Case 75-5 and applied here to Engineer F's non-engineering contractor misconduct - was reconciled with the ordinarily bounded jurisdiction of the engineering ethics code by invoking the nature of the underlying conduct rather than the domain of the license. The Board's reasoning implicitly holds that the ethics code's jurisdiction extends beyond PE practice whenever the conduct in question directly implicates the same integrity norms - honesty, non-deception, faithful agency, and protection of public safety - that the code exists to enforce. Engineer F's act of lending his contractor license number to an unlicensed individual unrelated to his firm is not merely a regulatory infraction in a separate domain; it is a paradigmatic integrity violation that mirrors the very harms the engineering ethics code guards against: misrepresentation of qualifications, facilitation of unlicensed practice, and endangerment of public safety in a safety-critical field. The Domain-Relevance Amplification principle further reinforces this synthesis: because fire sprinkler contracting is directly safety-critical, the revocation carries heightened materiality that closes any residual gap between the contractor domain and the PE ethics domain. This case therefore teaches that the Whole-Person Character Integrity Standard activates - and overrides any domain-boundedness objection - when three conditions converge: (1) the non-PE conduct reflects an adjudicated integrity violation, (2) the violation mirrors core engineering ethics norms, and (3) the domain of the violation is safety-sensitive.
Does the Allegation-Adjudication Distinction - which the Board used to differentiate Engineer F's case from BER 97-11 - conflict with the Prudential Disclosure principle applied to Engineer A, and does that conflict suggest that adjudicated findings always trigger disclosure while mere allegations never do, or is there a more nuanced threshold?
The Board's reasoning, read in light of its comparative analysis distinguishing BER Case 97-11, establishes a meaningful threshold: an adjudicated finding of wrongdoing - as opposed to a pending allegation or unresolved complaint - triggers a firm disclosure obligation on a professional employment application even when the disciplinary action arose outside the PE license domain. This allegation-adjudication distinction is not merely procedural; it reflects the epistemic difference between an unproven claim and a formally determined fact about the applicant's character. Because Engineer F's contractor license revocation was a completed adjudication, he could not invoke the uncertainty or reputational-harm rationale that might counsel caution about disclosing unresolved allegations. Furthermore, the Board's reasoning implies a continuing obligation: once hired, Engineer F's duty as a faithful agent and trustee to his employer would independently require disclosure of the revocation, since concealing a material adjudicated integrity finding from an employer who would reasonably consider it relevant to the employment relationship is inconsistent with the faithful agency canon. The ethical obligation thus did not expire at the moment of hiring but persisted as a relational duty throughout the employment relationship.
The Allegation-Adjudication Distinction drawn by the Board to differentiate Engineer F's case from BER Case 97-11 does not establish a binary rule that allegations never trigger disclosure while adjudications always do. Rather, it identifies adjudication as a sufficient condition for disclosure - a threshold that, once crossed, removes the prudential weighing that Engineer A in BER 97-11 was permitted to perform. Engineer A faced an unresolved allegation whose truth was contested and whose disclosure could itself cause harm; the Board recognized that a pending complaint does not carry the same evidentiary weight as a completed proceeding. Engineer F faced a formally adjudicated revocation - a finding of fact by a competent authority that the misconduct occurred. The distinction is not categorical but evidentiary: adjudication eliminates the uncertainty that justified Engineer A's more cautious approach and replaces it with a settled factual record that the engineer cannot in good faith treat as ambiguous or unresolved. Between the poles of mere allegation and formal adjudication lies a spectrum of intermediate findings - consent orders, informal settlements, deferred revocations - each of which would require its own materiality analysis.
The tension between Employment Application Question Scope Fidelity - the idea that an applicant may legitimately confine answers to the literal scope of a question - and the Technically True But Misleading Statement Prohibition was resolved decisively in favor of the latter. The Board implicitly held that when a question's evident purpose is to assess character and fitness for professional trust, an engineer cannot exploit narrow drafting to suppress a material adjudicated integrity violation. The narrow wording of the application question ('disciplined in the practice of professional engineering or had his license suspended or revoked') did not exculpate Engineer F because the ethics code imposes a duty to interpret such questions according to their evident purpose rather than their most self-serving literal reading. This resolution teaches that Question Scope Fidelity is a subordinate principle: it governs genuinely ambiguous or irrelevant omissions, but it yields entirely when the omitted information is both material to the questioner's evident purpose and reflects an adjudicated finding of wrongdoing by the applicant. The principle hierarchy is therefore: Technically True But Misleading Statement Prohibition > Employment Application Question Scope Fidelity, whenever the gap between literal scope and evident purpose is exploited to conceal integrity-relevant conduct.
The Allegation-Adjudication Distinction - used to differentiate Engineer F's case from BER Case 97-11, where Engineer A faced only a pending ethics complaint - resolves a latent tension between the Prudential Disclosure principle and the Omission Materiality principle by establishing a graduated disclosure threshold rather than a binary rule. Under BER 97-11, the Board declined to impose a categorical obligation on Engineer A to disclose a mere allegation, recognizing that unresolved complaints carry uncertain probative weight and that premature disclosure could itself be misleading or unfair. In Engineer F's case, however, the contractor license revocation is an adjudicated finding: a formal governmental determination that Engineer F committed a specific integrity violation. The synthesis of these two cases teaches that the disclosure obligation is calibrated to epistemic certainty and adjudicative finality: allegations occupy a zone of prudential weighing where disclosure may be advisable but is not categorically required, while adjudicated findings of wrongdoing - particularly those involving integrity violations in safety-sensitive domains - cross a threshold of materiality that makes non-disclosure on a professional employment application an ethics violation. The principle hierarchy is therefore: Omission Materiality (adjudicated findings) > Prudential Disclosure (allegations), with the Allegation-Adjudication Distinction serving as the operative boundary between the two regimes. This also implies that the moral responsibility for the informational gap created by the firm's narrow application drafting diminishes as the certainty and severity of the undisclosed finding increases - Engineer F cannot shift responsibility to the firm's imprecise drafting when the omitted fact is an adjudicated revocation for an integrity violation.
Does the Domain-Relevance Amplification principle - which heightens disclosure obligations when the prior misconduct occurred in a safety-sensitive field like fire protection - conflict with the Omission Materiality principle's domain-neutral standard, and should disclosure obligations be calibrated to the safety stakes of the prior domain or applied uniformly regardless of subject matter?
The fact that Engineer F's misconduct - lending his contractor license number to an unrelated unlicensed individual - directly implicates the same professional integrity norms that govern PE licensure creates a heightened, not merely equivalent, disclosure obligation. Licensing systems across engineering and contracting domains share a common foundational purpose: ensuring that only qualified, accountable individuals perform work that affects public safety. When an engineer subverts that system in one licensed domain by enabling unlicensed practice, the conduct speaks directly to his fitness to be trusted with the responsibilities of PE licensure in another. The fire protection context amplifies this further: fire sprinkler systems are life-safety infrastructure, and allowing an unlicensed individual to operate under a contractor license number in that domain is not a technical irregularity but a public safety violation. The cross-domain integrity relevance and the safety-critical nature of the field together elevate the materiality of the revocation well beyond what would apply to a license revocation in an unrelated, non-safety-sensitive domain.
The Whole-Person Character Integrity Standard - drawn from BER Case 75-5 and applied here to Engineer F's non-engineering contractor misconduct - was reconciled with the ordinarily bounded jurisdiction of the engineering ethics code by invoking the nature of the underlying conduct rather than the domain of the license. The Board's reasoning implicitly holds that the ethics code's jurisdiction extends beyond PE practice whenever the conduct in question directly implicates the same integrity norms - honesty, non-deception, faithful agency, and protection of public safety - that the code exists to enforce. Engineer F's act of lending his contractor license number to an unlicensed individual unrelated to his firm is not merely a regulatory infraction in a separate domain; it is a paradigmatic integrity violation that mirrors the very harms the engineering ethics code guards against: misrepresentation of qualifications, facilitation of unlicensed practice, and endangerment of public safety in a safety-critical field. The Domain-Relevance Amplification principle further reinforces this synthesis: because fire sprinkler contracting is directly safety-critical, the revocation carries heightened materiality that closes any residual gap between the contractor domain and the PE ethics domain. This case therefore teaches that the Whole-Person Character Integrity Standard activates - and overrides any domain-boundedness objection - when three conditions converge: (1) the non-PE conduct reflects an adjudicated integrity violation, (2) the violation mirrors core engineering ethics norms, and (3) the domain of the violation is safety-sensitive.
From a deontological perspective, did Engineer F fulfill his categorical duty of honesty by answering 'no' to the employment application's disciplinary question, given that the question's literal wording referenced only professional engineering license discipline while his contractor's license had been formally revoked for a clear integrity violation?
From a deontological perspective, Engineer F did not fulfill his categorical duty of honesty by answering 'no' to the employment application's disciplinary question. Kantian ethics requires not merely that statements be literally true but that they be offered in a spirit consistent with the rational agency of the recipient - that is, that they not be designed to produce a false belief in the listener's mind. Engineer F's answer, while technically accurate as to PE license discipline, was crafted to exploit the question's narrow wording in a way that would predictably cause the hiring firm to believe no relevant disciplinary history existed. This is precisely the kind of deception by omission that deontological ethics condemns as a violation of the duty of truthfulness. The categorical imperative further condemns the underlying maxim: if all engineers were permitted to answer disciplinary questions by reference only to the narrowest possible reading of the question's literal scope, the entire institution of employment application disclosure would be rendered meaningless. Engineer F's conduct fails both the universalizability test and the duty of non-deception.
From a virtue ethics standpoint, does Engineer F's deliberate reliance on the narrow wording of the employment application question to omit a material adjudicated integrity violation reflect the character of a professional who embodies honesty and integrity as stable virtues, or does it reveal a disposition toward legalistic self-protection incompatible with the whole-person integrity standard expected of licensed engineers?
From a virtue ethics standpoint, Engineer F's deliberate reliance on the narrow wording of the employment application question to omit an adjudicated integrity violation reveals a disposition toward legalistic self-protection that is fundamentally incompatible with the whole-person integrity standard expected of licensed professional engineers. A person of genuine honesty and integrity does not scan a question for its narrowest defensible reading in order to withhold information the questioner would plainly want to know. That behavior reflects not the stable virtue of honesty but its simulacrum - a performance of technical compliance designed to achieve the benefits of candor's reputation without its substance. The virtue ethics framework asks what a person of good character would do; a person of good character in Engineer F's position would have recognized that the hiring firm's evident purpose was to assess fitness and integrity, and would have disclosed the revocation voluntarily, perhaps with context, rather than exploiting a drafting gap. Engineer F's conduct is not merely a rule violation; it is a character revelation.
From a consequentialist perspective, did Engineer F's omission of the contractor license revocation on his employment application produce net harm by depriving the hiring firm of material information needed to assess his trustworthiness, and does the downstream erosion of employer-employee trust once the revocation was discovered outweigh any benefit Engineer F gained by securing the position through a technically accurate but misleading answer?
From a consequentialist perspective, Engineer F's omission produced net harm across multiple dimensions. The immediate harm was informational: the hiring firm was deprived of material data needed to make an informed employment decision, potentially placing Engineer F in a role for which the firm would not have hired him had it known the full record. The downstream harm was relational: when the firm independently discovered the revocation, the trust foundation of the employment relationship was retroactively compromised - not only by the original misconduct but by the deliberate concealment, which is often more damaging to professional relationships than the underlying act. The systemic harm was institutional: if engineers are permitted to exploit narrow application wording to conceal adjudicated integrity violations, the reliability of professional employment disclosures as a screening mechanism is eroded for the entire profession. Against these harms, the benefit to Engineer F - securing a position he might not otherwise have obtained - is both self-interested and contingent on the concealment remaining undiscovered. A consequentialist calculus that accounts for discovery probability, relational harm, and systemic effects yields a clear verdict against the omission.
From a deontological perspective, does the NSPE Code's duty to act as a faithful agent and trustee impose on Engineer F an obligation to interpret the employment application's disciplinary question according to its evident purpose-assessing character and fitness-rather than its narrowest literal scope, such that omitting an adjudicated non-PE license revocation constitutes a breach of duty regardless of the question's precise wording?
From a deontological perspective, the NSPE Code's duty to act as a faithful agent and trustee does impose on Engineer F an obligation to interpret the employment application's disciplinary question according to its evident purpose rather than its narrowest literal scope. The faithful agent duty is not merely a duty to avoid active deception; it is an affirmative duty to serve the principal's legitimate informational interests. A hiring firm's evident purpose in asking about disciplinary history is to assess character and fitness - not to conduct a technical exercise in license-category taxonomy. An engineer who interprets such a question by its narrowest literal scope, knowing that the interpretation will produce a materially false impression, is not acting as a faithful agent; he is acting as an adversarial party seeking to minimize disclosure. The deontological duty of fidelity requires that Engineer F ask not 'what is the minimum I must disclose under the strictest reading of this question?' but rather 'what information does my principal need to make an informed decision?' The answer to the latter question clearly includes the contractor license revocation.
If Engineer F had voluntarily disclosed the contractor license revocation on the employment application before being hired, would the engineering firm have been ethically and practically better positioned to make an informed hiring decision, and would proactive disclosure have mitigated or eliminated the integrity concerns that arose when the firm independently discovered the omission?
Had Engineer F voluntarily disclosed the contractor license revocation on the employment application - ideally with a brief contextual explanation of the circumstances and any remedial steps taken - the engineering firm would have been materially better positioned to make an informed hiring decision, and the integrity concerns that arose upon independent discovery would have been substantially mitigated or eliminated. Proactive disclosure transforms the character signal from concealment to candor: an applicant who discloses an adverse history before being asked demonstrates the very honesty and self-awareness that a hiring firm seeks in a professional engineer. The firm might still have declined to hire Engineer F, but that outcome would reflect a legitimate exercise of informed judgment rather than a trust betrayal. More importantly, if the firm had hired Engineer F with full knowledge of the revocation, the subsequent discovery would carry no additional sting - there would be nothing to discover that was not already known. The ethical and practical case for proactive disclosure is therefore not merely deontological but prudential: it is the strategy most consistent with long-term professional integrity and relational trust.
If the employment application had been drafted more broadly-asking whether the applicant had ever had any professional or occupational license suspended, revoked, or disciplined in any field-would Engineer F have been compelled to disclose the contractor license revocation, and does the firm's failure to draft such a comprehensive question share any moral responsibility for the informational gap that resulted?
If the employment application had been drafted more broadly - asking whether the applicant had ever had any professional or occupational license of any kind suspended, revoked, or disciplined - Engineer F would unambiguously have been compelled to disclose the contractor license revocation, and his failure to do so under such a question would have constituted an outright false statement rather than a misleading omission. The firm's failure to draft such a comprehensive question does reflect a due diligence gap, but that gap does not bear significant moral weight in distributing responsibility for the informational deficit. The ethical obligation to disclose material integrity information is not contingent on the questioner's drafting sophistication; it flows from the engineer's own affirmative duties under the Code. The firm's imprecise drafting created an opportunity for evasion that Engineer F exploited, but the exploitation itself - not the opportunity - is the ethical violation. A more comprehensive question would have eliminated the ambiguity Engineer F relied upon, but the absence of such a question did not create a moral permission to conceal.
If Engineer F's contractor license revocation had involved a domain entirely unrelated to engineering-such as a food service or real estate license-rather than fire sprinkler contracting, which directly implicates public safety and fire protection, would the ethical obligation to disclose on a professional engineering employment application be weaker, and does the safety-critical nature of fire protection work amplify the materiality of the revocation to the point where disclosure would be required even under a narrow reading of the application question?
If Engineer F's contractor license revocation had involved a domain entirely unrelated to engineering - such as a food service or real estate license - the ethical obligation to disclose on a PE employment application would be weaker, though not necessarily absent. The materiality of a non-PE license revocation to a PE employment application is a function of two variables: the character relevance of the underlying conduct and the domain relevance of the licensed activity. A food service license revocation for a health code violation speaks primarily to regulatory compliance in an unrelated field and carries limited character signal for PE fitness. A real estate license revocation for misrepresentation would carry stronger character relevance because it implicates honesty directly, even though the domain is unrelated. Engineer F's contractor license revocation in fire sprinkler contracting scores high on both variables: the underlying conduct - enabling unlicensed practice - directly implicates professional integrity norms shared across all licensed professions, and the domain - fire protection - is a safety-critical field whose public welfare stakes are directly analogous to those that PE licensure is designed to protect. The safety-critical nature of fire protection work amplifies the materiality of the revocation and supports disclosure even under a narrow reading of the application question.
If Engineer F's situation had involved only an unresolved allegation of contractor misconduct-rather than a formal adjudicated revocation-would the ethical obligation to disclose on the employment application have been different, and how does the allegation-versus-adjudication distinction drawn in BER Case 97-11 apply to calibrate the disclosure threshold between Engineer A's pending complaint and Engineer F's completed revocation proceeding?
If Engineer F's situation had involved only an unresolved allegation of contractor misconduct - rather than a formal adjudicated revocation - the ethical obligation to disclose on the employment application would have been materially different and would have required the kind of prudential weighing that the Board in BER Case 97-11 permitted Engineer A to perform. An unresolved allegation is, by definition, a contested claim whose truth has not been established by a competent authority; disclosing it risks conveying a false negative impression based on an accusation that may ultimately be unfounded. The allegation-versus-adjudication distinction is therefore not merely procedural but epistemically significant: adjudication produces a settled factual record that the engineer cannot in good faith treat as ambiguous, while a pending allegation remains genuinely uncertain. Engineer F's case involved a completed revocation proceeding - an authoritative determination that the misconduct occurred - which eliminates the epistemic uncertainty that justified Engineer A's more cautious approach. The disclosure threshold calibration suggested by the two cases is: pending unresolved allegations permit prudential non-disclosure; formally adjudicated findings require disclosure, particularly when the underlying conduct implicates professional integrity.
Decisions & Arguments
View ExtractionCausal-Normative Links 4
- Engineer F Contractor License Revocation Non-Disclosure Employment Application
- Engineer F Technically True Misleading Answer Employment Application
- Engineer F Adjudicated Misconduct Employment Application Disclosure
- Engineer F Employment Application Contractor License Revocation Proactive Disclosure
- Engineer F Employer Question Intent Broad Interpretation Failure
- Engineer F Ethics Beyond Minimum Employment Disclosure Failure
- Engineer F Domain-Relevance Amplified Fire Protection Disclosure Failure
- Engineer F Artfully Misleading Employment Application Answer
- Engineer F Personal Misconduct Ethics Code Jurisdiction Recognition Failure
- Engineer F Non-Engineering License Disciplinary History Employment Disclosure Failure
- Engineer A Pending Complaint Limited Background Information Prudential Weighing BER 97-11
- Engineer F Qualifications Non-Misrepresentation Employment Application
- Engineer F Employer-Employee Trust Foundation Proactive Disclosure Failure
- Employer-Employee Trust Foundation Proactive Disclosure Obligation
- Engineer F Ethics Beyond Minimum Employment Disclosure Failure
- Ethics Beyond Minimum Employment Relationship Conduct Obligation
- Engineer F Adjudicated Misconduct Employment Application Disclosure Failure
- Engineer F Domain-Relevance Amplified Fire Protection Disclosure Failure
- Domain-Relevance Amplified Adjudicated Misconduct Disclosure Obligation
- Engineer F Ethics Code Supersession of Legalistic Minimum Employment Disclosure
- Engineer F Contractor License Number Lending Prohibition Violation
- Contractor License Number Lending Prohibition Obligation
- Engineer F Non-Engineering Professional License Revocation Character Disclosure
Decision Points 12
Should Engineer F disclose the contractor license revocation on the employment application, or answer 'no' based on the question's literal limitation to PE license discipline?
The Employment Application Question Scope Fidelity principle supports Engineer F's literal 'no' answer, since the question's text references only PE license discipline and his PE license was never disciplined. Against this, the Technically True But Misleading Statement Prohibition and the Ethics Minimum Non-Sufficiency Employment Disclosure Constraint establish that literal accuracy does not satisfy the Code when the overall impression conveyed is false: the evident purpose of the question was to assess character and fitness, not to audit PE license status in a narrow administrative sense. The Whole-Person Character Integrity Standard (BER 75-5) and the Domain-Relevance Amplification principle further establish that the contractor revocation, arising from an integrity violation in a safety-critical field directly analogous to PE public-safety obligations, is material to the employer's assessment regardless of the question's literal scope.
Uncertainty arises because if the hiring firm's narrow drafting is treated as a binding definition of the disclosure domain, Engineer F's literal answer is technically defensible and the moral responsibility for the informational gap shifts partly to the firm. Additionally, if Engineer F genuinely believed the question was limited to PE license matters and did not subjectively intend to deceive, the technically-true-but-misleading prohibition may not apply with full force. The rebuttal condition is defeated, however, by the adjudicated nature of the revocation, which eliminates epistemic uncertainty, and by the fire protection domain's direct safety relevance to PE practice.
Engineer F holds a PE license that was never suspended or revoked. He also held a contractor's license that was formally revoked after an adjudicated proceeding determined he allowed an unlicensed individual unrelated to his firm to use his contractor license number on a fire protection project. The employment application asks whether the applicant has ever been disciplined in the practice of professional engineering or had his engineering license suspended or revoked. Engineer F answers 'no,' which is literally accurate as to his PE license but omits the adjudicated contractor license revocation.
Should Engineer F proactively disclose the contractor license revocation to his employer after being hired, or treat the omission as closed once the application was submitted and the narrow question technically answered?
The Employer-Employee Trust Foundation Proactive Disclosure Obligation establishes that an engineer must disclose material adjudicated misconduct to an employer at the outset of, or during, the employment relationship, rather than allowing the employer to discover it through third parties, because post-hire discovery compounds the original omission into a relational betrayal. The Ethics Beyond Minimum Employment Relationship Conduct Obligation further requires that engineers exceed the minimum literal compliance with application questions and proactively disclose information a reasonable employer would consider material. Against these, the Employment Application Question Scope Fidelity principle might suggest that once Engineer F answered the question as posed, no further disclosure obligation arose absent a new triggering event. The firm's failure to draft a broader question (Hiring Firm Broad-Scope Disciplinary Inquiry Due Diligence Obligation) could also be read as partially redistributing moral responsibility for the informational gap to the firm.
Uncertainty is created by the absence of a defined trigger event for the continuing post-hire obligation, if no new circumstance arose (such as assignment to a fire protection project) that made the revocation newly relevant, it is unclear at what moment the continuing duty crystallized. Additionally, if the firm's narrow drafting is treated as a binding definition of the disclosure domain, the argument that Engineer F bore a continuing obligation beyond the application's literal scope is weakened. These rebuttals are overcome by the adjudicated nature of the revocation and the fact that Engineer F knew the employer was operating under a materially incomplete understanding of his professional record, a condition he himself created, making silence an ongoing ethical breach rather than a neutral omission.
Engineer F was hired after answering 'no' to the disciplinary question on the employment application. The engineering firm subsequently discovers, through third parties rather than from Engineer F, that his contractor's license was revoked for allowing an unlicensed individual to use his license number on a fire protection project. At no point after being hired did Engineer F voluntarily disclose the revocation to his employer. The firm's application question was narrowly drafted to reference only PE license discipline, which Engineer F relied upon to justify his original omission.
Should the board treat Engineer F's adjudicated contractor license revocation as categorically requiring disclosure, distinguishing it from the mere allegation Engineer A faced in BER 97-11, or apply the same prudential weighing standard that permitted Engineer A to exercise discretion about disclosure?
The Allegation-Adjudication Distinction establishes that a formally adjudicated finding, unlike a pending allegation, produces a settled factual record that eliminates the epistemic uncertainty justifying prudential non-disclosure. Engineer A could reasonably weigh the risks of disclosing an unproven claim; Engineer F cannot in good faith treat an adjudicated revocation as ambiguous or unresolved. The Omission Materiality principle further establishes that adjudicated findings of integrity violations cross a materiality threshold that makes non-disclosure on a professional employment application an ethics violation. Against this, the Prudential Disclosure principle applied to Engineer A might be extended to Engineer F on the grounds that the contractor license domain is sufficiently remote from PE practice that the same discretionary weighing should apply.
Uncertainty is created by the rebuttal condition that prudential disclosure can apply even absent adjudication, meaning the allegation-adjudication distinction does not establish a clean binary rule, and that if an adjudication were in a domain entirely remote from engineering, the same categorical disclosure obligation might not follow. Additionally, the board in BER 97-11 did not hold that Engineer A was prohibited from disclosing; it held that automatic disclosure was not required. A parallel reading might suggest Engineer F had discretion to disclose or not, rather than a categorical obligation. These rebuttals are overcome by the combination of adjudicative finality, the integrity-implicating character of the underlying conduct, and the fire protection domain's direct safety relevance to PE obligations.
In BER Case 97-11, Engineer A faced a pending ethics complaint, an unresolved allegation, and the board declined to impose a categorical disclosure obligation, instead permitting prudential weighing of whether to provide limited background information to the client. Engineer F's situation differs materially: his contractor license was formally revoked through a completed adjudicatory proceeding that determined he committed a specific integrity violation (license number lending to an unlicensed individual). His PE license was never disciplined. The question is whether the allegation-adjudication distinction justifies treating Engineer F's disclosure obligation as categorically stronger than Engineer A's.
Should Engineer F disclose the contractor license revocation on the employment application despite the question's narrow wording, or answer 'no' on the ground that the question literally covers only PE license discipline?
The NSPE Code's prohibition on deceptive acts and material omissions (Technically True But Misleading Statement Prohibition) requires that the overall impression conveyed be truthful, not merely that individual statements be literally accurate. The Whole-Person Character Integrity Standard (BER 75-5) extends ethical scrutiny to non-engineering conduct when it bears on honesty and fitness. Domain-Relevance Amplification heightens materiality because fire sprinkler contracting is safety-critical and the underlying conduct, enabling unlicensed practice, mirrors core engineering integrity norms. Against these, Employment Application Question Scope Fidelity holds that an applicant may legitimately confine answers to the literal scope of the question posed, and the firm's narrow drafting could be read as defining the disclosure domain.
Uncertainty arises because if the hiring firm's narrow drafting is treated as a binding definition of the disclosure domain, the warrant for proactive disclosure loses direct force. Engineer F could argue he answered the question asked. The rebuttal is further supported if Engineer F genuinely believed the question was limited to PE license matters and did not subjectively intend to deceive. However, the board resolved this by holding that the evident purpose of the question, assessing character and fitness, governs its ethical scope, and that a technically accurate answer designed to exploit imprecise drafting is ethically equivalent to a misrepresentation when the omitted information is material.
Engineer F held a fire sprinkler contractor license that was formally revoked after an adjudicated proceeding determined he had allowed an unlicensed individual unrelated to his firm to use his contractor license number. His PE license was not suspended. When applying to an engineering firm, the employment application asked whether the applicant had been disciplined in the practice of professional engineering or had a PE license suspended or revoked. Engineer F answered 'no.' The firm later independently discovered the contractor license revocation.
After being hired without disclosing the contractor license revocation, should Engineer F proactively inform his employer of the revocation, or remain silent unless the employer independently discovers it?
The NSPE Code's faithful agent and trustee canon imposes an affirmative, continuing duty of candor regarding material facts bearing on fitness and integrity, not merely a duty to avoid active deception at the moment of application. Silence in the face of a known material omission, once an employment relationship is established, compounds rather than cures the original ethical breach. The Ethics Beyond Minimum Employment Relationship Conduct Obligation holds that the Code's standards exceed the legal minimum and require proactive disclosure when the employer is operating under a materially false impression the engineer created. Against these, the absence of a defined trigger event for the continuing obligation creates uncertainty about when exactly the duty crystallizes post-hire.
Uncertainty is created by the absence of a defined trigger event for the continuing obligation, if no new circumstance arises post-hire (such as assignment to a fire protection project), Engineer F might argue the original omission was a closed matter and that volunteering the information unprompted would be supererogatory rather than obligatory. Additionally, Engineer F might contend that the privacy interest in past disciplinary matters not directly implicated by current work provides a competing reason for silence. The board resolved this by holding that the disclosure obligation crystallizes at the latest when the employer's reliance on the incomplete record becomes consequential, and that the faithful agent duty is not bounded by the moment of application.
Engineer F was hired by the engineering firm after answering 'no' to the employment application's disciplinary question, creating a materially incomplete record in the firm's files. Once employed, Engineer F entered a fiduciary-adjacent relationship with his employer as a faithful agent and trustee under the NSPE Code. The firm subsequently discovered the contractor license revocation independently. At no point between hiring and discovery did Engineer F voluntarily disclose the revocation to his employer.
Should the engineering firm interpret its employment application disciplinary question according to its evident purpose, capturing any adjudicated professional misconduct, or accept that its narrow literal drafting confined Engineer F's disclosure obligation to PE license matters only?
The Hiring Firm Broad-Scope Disciplinary Inquiry Due Diligence Obligation holds that a firm seeking to assess character and fitness should draft application questions comprehensive enough to capture adjudicated misconduct across all professional and occupational license domains. The Employer Question Intent Broad Interpretation Disclosure Obligation holds that the firm's evident purpose, assessing fitness, should govern how the question is interpreted, regardless of its literal scope. Against these, the firm's imprecise drafting could be read as defining the disclosure domain, and distributing some moral responsibility for the informational gap to the firm rather than placing it entirely on the applicant.
The firm's shared-responsibility argument is rebutted if the NSPE Code's Ethics Higher Standard Than Legal Minimum principle imposes on engineers an affirmative duty to volunteer material integrity information regardless of question precision, in which case the firm's drafting gap is a due diligence failure but not a moral license for the applicant to conceal. The board resolved this by holding that the ethical obligation to disclose flows from the engineer's own Code duties, not from the sophistication of the questioner's drafting, and that the firm's imperfect drafting constitutes a due diligence gap but does not bear significant moral weight in distributing responsibility for the omission.
The engineering firm's employment application asked whether the applicant had been disciplined 'in the practice of professional engineering' or had a PE license suspended or revoked. The question did not ask about contractor licenses, occupational licenses in other fields, or adjudicated disciplinary proceedings outside the PE domain. Engineer F answered 'no,' and the firm hired him. The firm later independently discovered that Engineer F's fire sprinkler contractor license had been formally revoked for an integrity violation. The firm's narrow drafting created an ambiguity that Engineer F exploited.
Should Engineer F disclose the contractor license revocation on the employment application despite the question's narrow wording referencing only professional engineering license discipline, or answer 'no' based on the question's literal scope?
Two competing obligations are in tension. First, the Employment Application Question Scope Fidelity Obligation holds that an engineer may legitimately confine answers to the literal scope of the question posed, and that the firm bears some responsibility for drafting a comprehensive inquiry. Second, the Technically True But Misleading Statement Prohibition, reinforced by the Employer Question Intent Broad Interpretation Obligation and the Faithful Agent and Trustee duty, holds that the evident purpose of the disciplinary question was to assess character and fitness, not to audit PE license status in a narrow administrative sense, and that exploiting imprecise drafting to conceal an adjudicated integrity violation constitutes a deceptive omission regardless of literal accuracy. The Domain-Relevance Amplification principle further heightens the obligation because fire sprinkler contracting is a safety-critical field whose public-safety stakes mirror those of PE licensure.
Uncertainty arises because if the hiring firm's narrow drafting is treated as a binding definition of the disclosure domain, the warrant for proactive disclosure may not apply: the engineer could argue he answered exactly what was asked. Additionally, if Engineer F genuinely believed the question was confined to PE license matters and did not subjectively intend to deceive, the technically-true-but-misleading prohibition may not be triggered under a subjective-intent reading. The firm's failure to draft a comprehensive question could be argued to bear some moral weight in distributing responsibility for the informational gap.
Engineer F's contractor license was formally revoked after an adjudicated proceeding for allowing an unlicensed individual unrelated to his firm to use his contractor license number in the fire sprinkler contracting domain. The employment application asked whether the applicant had been disciplined 'in the practice of professional engineering' or had his PE license suspended or revoked. Engineer F answered 'no,' which was technically accurate as to his PE license but omitted the adjudicated contractor license revocation. The hiring firm was unaware of the revocation at the time of hire and later discovered it independently.
Should Engineer F proactively disclose the contractor license revocation to his employer after being hired, or maintain silence on the grounds that the employment relationship has already been established and no new triggering event has occurred?
The Employer-Employee Trust Foundation Proactive Disclosure Obligation holds that once hired, an engineer's duty as a faithful agent and trustee independently activates a continuing obligation of candor regarding material facts bearing on fitness and integrity, the disclosure obligation does not expire at the moment of application submission. The Ethics Beyond Minimum Employment Relationship Conduct Obligation reinforces that the NSPE Code imposes a higher standard than the legal minimum, requiring proactive disclosure of material integrity information even absent a direct inquiry. Against these, the Employment Application Question Scope Fidelity principle and a narrow reading of the faithful-agent duty (as governing conduct toward clients and the public rather than employers) could suggest that no new obligation arose post-hire absent a specific triggering event such as assignment to a fire protection project.
Uncertainty is created by the absence of a defined trigger event for the continuing obligation, if no new circumstance arises post-hire (such as a project assignment in the fire protection domain or a direct employer inquiry), it is unclear precisely when the continuing duty crystallizes. Additionally, if the faithful-agent duty is construed as governing conduct toward clients and the public rather than toward employers, the post-hire disclosure obligation may lack a clear Code anchor. An engineer might also argue that voluntary post-hire disclosure, absent a direct inquiry, exceeds what the Code affirmatively requires.
Engineer F was hired by the engineering firm without disclosing the contractor license revocation. After hire, Engineer F continued to work without informing his employer of the adjudicated revocation. The firm subsequently discovered the revocation independently. At the time of post-hire non-disclosure, Engineer F was operating as an employee in a fiduciary-adjacent relationship with his employer under the NSPE Code's faithful agent and trustee canon, and the employer was relying on a materially incomplete understanding of Engineer F's professional history, an understanding Engineer F himself had created through omission on the application.
Should the Engineering Firm Hiring Authority disclose Engineer F's adjudicated contractor license revocation to relevant parties, such as clients, project teams, or licensing authorities, upon discovering it, or treat the matter as an internal employment issue requiring no external disclosure?
The Domain-Relevance Amplified Adjudicated Misconduct Disclosure Obligation holds that when a firm discovers an employee's adjudicated integrity violation in a safety-critical domain, the firm's own duties under the public safety paramount canon may require disclosure to parties whose interests are affected, particularly clients on active projects where Engineer F's fitness and trustworthiness are material. The Employer-Employee Trust Foundation Proactive Disclosure Obligation, read from the firm's perspective, supports internal remediation and potentially external notification where public safety is implicated. Against this, treating the matter as an internal employment decision, taking corrective action with Engineer F without external disclosure, is defensible if no active project safety risk is identified and the revocation predates the employment relationship.
Uncertainty arises because the firm's disclosure obligation to external parties depends heavily on whether Engineer F is currently assigned to projects where the revocation is materially relevant to client trust or public safety. If the revocation is in a domain sufficiently remote from the firm's current work, or if Engineer F has been reassigned or terminated, the case for external disclosure weakens. Additionally, the firm's own due diligence gap, its failure to draft a comprehensive disciplinary inquiry question, may complicate its moral standing to take aggressive external action, though this does not eliminate its public-safety obligations.
The engineering firm independently discovered Engineer F's contractor license revocation after he had been hired. The revocation arose from an adjudicated proceeding in the fire sprinkler contracting domain, a safety-critical field, for allowing an unlicensed individual to use his contractor license number. The firm had not been informed of the revocation at the time of hire because Engineer F answered 'no' to the application's disciplinary question, which was narrowly worded to reference only PE license discipline. The firm must now decide how to respond to the discovery, including whether any disclosure obligation runs to clients, project stakeholders, or regulatory bodies.
Should Engineer F disclose the contractor license revocation on the employment application despite the question's narrow wording referencing only PE license discipline, or rely on the literal scope of the question to justify omitting the revocation?
Competing obligations include: (1) the Technically True But Misleading Statement Prohibition, which holds that literal accuracy does not satisfy the Code when the overall impression conveyed is false and material information is suppressed; (2) the Whole-Person Character Integrity Standard (BER 75-5), which extends ethical scrutiny to non-engineering conduct bearing on honesty and public safety; (3) the Ethics Code Supersession of Legalistic Minimum principle, which holds that the Code imposes affirmative duties beyond the minimum a narrow question might technically require; against (4) the Employment Application Question Scope Fidelity Obligation, which holds that an engineer may legitimately confine answers to the literal scope of the question posed.
Uncertainty arises because if the hiring firm's narrow drafting is treated as a binding definition of the disclosure domain, the warrant for proactive disclosure does not activate. Engineer F's answer would be both literally accurate and within the question's stated scope. Additionally, if the NSPE Code's jurisdiction is held to be bounded by PE practice, the whole-person standard may not reach a contractor license matter. The rebuttal is weakened, however, by the adjudicated nature of the revocation, the integrity-implicating character of the underlying conduct, and the safety-critical domain of fire sprinkler contracting.
Engineer F held a contractor license for fire sprinkler work that was formally revoked after an adjudicated proceeding determined he had allowed an unrelated unlicensed individual to use his license number. His PE license was not suspended. On a PE employment application, a disciplinary question asked only about discipline 'in the practice of professional engineering.' Engineer F answered 'no.' The hiring firm later independently discovered the revocation.
After being hired without disclosing the contractor license revocation, should Engineer F proactively disclose the revocation to his employer, or maintain silence on the grounds that the application process has concluded and no new triggering event has occurred?
Competing obligations include: (1) the Employer-Employee Trust Foundation Proactive Disclosure Obligation, which holds that the faithful agent and trustee duty activates an independent, continuing obligation of candor regarding material facts bearing on fitness and integrity throughout the employment relationship; (2) the Ethics Beyond Minimum Employment Relationship Conduct Obligation, which holds that the Code imposes affirmative duties that exceed the legalistic minimum of answering only what was asked at the application stage; against (3) the absence of a defined post-hire trigger event, if no new circumstance arises (such as a project assignment in the fire protection domain), the argument that silence is permissible once the application process has concluded carries some weight.
Uncertainty is created by the absence of a defined trigger event for the continuing obligation. If no new circumstance arises post-hire that makes the revocation newly relevant, such as assignment to fire protection projects or supervisory authority over licensed work, the argument that the disclosure window closed with the application process has surface plausibility. Additionally, if the NSPE Code's faithful agent duty is construed as governing conduct toward clients and the public rather than toward employers, the continuing obligation may not independently activate. These rebuttals are weakened by the fact that Engineer F himself created the informational gap through omission, and that the employer's reliance on the incomplete record becomes consequential from the moment of hire.
Engineer F was hired without disclosing the contractor license revocation. Once employed, he entered a fiduciary-adjacent relationship with his employer as a faithful agent and trustee under the NSPE Code. The employer was operating under a materially incomplete understanding of Engineer F's professional history, an understanding Engineer F himself had created through omission. The firm subsequently discovered the revocation independently, at which point the trust foundation of the employment relationship was retroactively compromised both by the original misconduct and by the deliberate concealment.
Should Engineer F treat the adjudicated contractor license revocation as triggering a categorical, non-waivable disclosure obligation on the employment application, foreclosing any prudential weighing, or apply the same discretionary balancing that BER 97-11 permitted Engineer A to perform regarding an unresolved allegation?
Competing obligations include: (1) the Allegation-Adjudication Distinction, which holds that adjudication produces a settled factual record eliminating the epistemic uncertainty that justified Engineer A's more cautious approach, making non-disclosure an ethics violation rather than a permissible prudential choice; (2) Domain-Relevance Amplification, which heightens the materiality of the revocation because fire sprinkler contracting is safety-critical and the underlying conduct mirrors core engineering ethics violations; (3) the Omission Materiality principle, which holds that adjudicated integrity findings cross a materiality threshold making non-disclosure impermissible; against (4) the Prudential Disclosure principle, which holds that engineers may weigh reputational harm and contextual factors when deciding whether to disclose adverse history, particularly when the prior proceeding arose outside the PE domain.
Uncertainty is created by the possibility that prudential disclosure can apply even to adjudicated findings if the domain is sufficiently remote from engineering: for example, a food service license revocation would not obviously trigger the same categorical obligation. Additionally, if the adjudication were in a domain entirely unrelated to engineering competence or public safety, the domain-relevance amplification principle would not activate, and the whole-person standard might not reach the conduct. These rebuttals are foreclosed here because fire sprinkler contracting is directly safety-critical and the underlying conduct, enabling unlicensed practice, mirrors paradigmatic engineering ethics violations.
Engineer F's contractor license was formally revoked through a completed adjudicative proceeding, a governmental determination that he committed a specific integrity violation by allowing an unlicensed individual to use his license number in fire sprinkler contracting. His PE license was not suspended. In BER Case 97-11, Engineer A faced only a pending, unresolved ethics complaint and was permitted to weigh prudentially whether to disclose it to a client. Engineer F's situation involves a completed revocation, not a pending allegation, in a safety-critical domain directly analogous to PE public-safety obligations.
Event Timeline
Causal Flow
- Non-Disclosure_to_Active_Client_(BER_97-11_Precedent) Unlicensed Individual License Sharing
- Unlicensed Individual License Sharing Negative Disclosure Answer on Application
- Negative Disclosure Answer on Application Post-Hire_Non-Disclosure_of_Revocation
- Post-Hire_Non-Disclosure_of_Revocation Contractor License Revocation
Opening Context
View ExtractionYou are Engineer F, a professional engineer applying for a position at an engineering firm. The employment application includes a question asking whether you have ever been disciplined in the practice of professional engineering or had your license suspended or revoked. Your PE license has never been suspended or revoked, but your contractor's license for a fire sprinkler contracting firm you previously owned was revoked after you allowed an unlicensed individual unaffiliated with your firm to use your contractor license number on a separate project. The application question is worded narrowly, referencing only professional engineering license discipline. The decisions you face now will determine how your professional obligations intersect with the boundaries of what was explicitly asked.
Characters (6)
A licensed PE and former contracting firm owner whose contractor's license was revoked for improperly lending his license number, who then omitted this disciplinary history on a subsequent engineering employment application.
- Likely motivated by self-preservation and career advancement, calculating that the revocation of a contractor's license — distinct from his PE license — fell outside the spirit of the application question and would not surface during hiring review.
A professional engineering employer that administered a disciplinary disclosure question on its employment application and later discovered through independent means that a candidate had concealed a contractor's license revocation.
- Motivated to protect the firm's professional reputation, liability exposure, and ethical standing by ensuring that hired engineers meet standards of honesty and full disclosure, prompting scrutiny once the omission came to light.
A practicing engineer retained for design and scheduling services who faced a pending ethics complaint from a former client alleging incompetence but chose not to proactively inform his current client of that complaint.
- Likely motivated by a desire to protect his professional reputation and retain the current engagement, judging — perhaps reasonably but imperfectly — that an unresolved, unproven complaint did not rise to the level of mandatory disclosure.
A client who retained Engineer A for manufacturing facility design and scheduling services and felt blindsided upon learning through a third party about a pending ethics complaint against their engineer.
- Motivated by a reasonable expectation of transparency and informed decision-making, believing that material information about an engineer's professional standing directly affects trust, project risk assessment, and the client's ability to make an educated retention decision.
Client C had previously engaged Engineer A for similar services and filed an ethics complaint with the state board alleging Engineer A lacked competence to perform those services.
Engineer F's employer asked Engineer F specifically about whether Engineer F had a license suspended or been disciplined in connection with the practice of professional engineering. The employer's question, while narrowly worded, sought to elicit information about Engineer F's character, integrity, and credibility as a professional engineer.
Tension between Employment Application Contractor License Revocation Proactive Disclosure Obligation and Ethics Minimum Non-Sufficiency Employment Disclosure Constraint
Tension between Employer-Employee Trust Foundation Proactive Disclosure Obligation and Safety-Domain Cross-License Integrity Heightened Disclosure Constraint
Tension between Engineer F Non-Engineering Professional License Revocation Character Disclosure and Employment Application Question Scope Fidelity Obligation
Tension between Engineer F Contractor License Revocation Non-Disclosure Employment Application and Employer-Employee Trust Foundation Proactive Disclosure Obligation
Tension between Employer Question Intent Broad Interpretation Disclosure Obligation and Hiring Firm Broad-Scope Disciplinary Inquiry Due Diligence Obligation
Tension between Engineer F Employer Question Intent Broad Interpretation Failure and Employment Application Question Scope Fidelity Obligation
Tension between Engineer F Employer-Employee Trust Foundation Proactive Disclosure Failure and Employer-Employee Trust Foundation Proactive Disclosure Obligation
Tension between Domain-Relevance Amplified Adjudicated Misconduct Disclosure Obligation and Post-Hire Non-Disclosure of Revocation
Tension between Engineer F Non-Engineering License Disciplinary History Employment Disclosure Failure and Employment Application Question Scope Fidelity Obligation
Tension between Engineer F Ethics Code Supersession of Legalistic Minimum Employment Disclosure and Post-Hire Non-Disclosure of Revocation
Tension between Engineer F Adjudicated Misconduct Employment Application Disclosure Failure and Engineer F BER 97-11 Allegation vs Adjudication Disclosure Threshold Distinction
Engineer F faces a genuine dilemma between the obligation to disclose adjudicated misconduct (contractor license revocation) on an employment application and the constraint established by BER 97-11 that distinguishes between mere allegations and formal adjudications as the disclosure threshold. While the adjudication threshold is met here — making disclosure obligatory — Engineer F may attempt to exploit the allegation/adjudication distinction as a legalistic shield, arguing the revocation pertains to a non-engineering license and thus falls below the disclosure threshold. Fulfilling the disclosure obligation requires affirmatively volunteering information that the constraint's threshold logic might appear to excuse, creating a tension between bright-line rule application and the spirit of honest disclosure.
Engineer F is obligated not to misrepresent qualifications on an employment application, yet the constraint of providing technically true but misleading answers creates a genuine dilemma. By answering application questions in a narrowly literal manner — for example, interpreting 'professional license disciplinary action' as referring only to engineering licenses and not contractor licenses — Engineer F can craft responses that are factually defensible but substantively deceptive. This tension pits the spirit of the non-misrepresentation obligation against the letter of the constraint, where legalistic evasion substitutes for genuine honesty. The dilemma is whether technical truth satisfies the ethical duty of non-misrepresentation, or whether the obligation demands proactive correction of foreseeable misimpressions.
The obligation to disclose adjudicated misconduct is amplified when the misconduct is domain-relevant — here, a contractor license revocation in fire protection directly bears on Engineer F's fitness for an engineering role in the same safety-critical domain. However, the constraint of ethics code jurisdictional limits (per BER 75-5) holds that engineering ethics codes do not straightforwardly govern personal or non-engineering professional conduct. This creates a genuine dilemma: the domain-relevance of the contractor misconduct morally demands disclosure and heightened scrutiny, yet the formal jurisdictional constraint suggests the ethics code may not compel disclosure of non-engineering license actions. Resolving this tension requires determining whether domain-relevance overrides jurisdictional formalism, particularly where public safety in fire protection engineering is at stake.
Opening States (10)
Key Takeaways
- Engineers have an affirmative ethical duty to disclose material information bearing on their character and fitness that goes beyond the literal scope of application questions, particularly when omission would create a misleading impression.
- A license revocation in any professional domain — not merely engineering — can constitute ethically relevant character information that must be disclosed in employment contexts, because professional integrity is not siloed by discipline.
- Relying on narrow, literal interpretations of disclosure questions to justify omission is ethically insufficient; the spirit and purpose of such questions demand candor that meets the reasonable expectations of a prospective employer.