
[EDRM Editor’s Note: The opinions and positions are those of Michael D. Berman.]
“Under the functional equivalent doctrine, where a consultant serves as a de facto employee of a company, communications between the consultant and the company’s lawyers are protected by the attorney-client privilege, and disclosure to the consultant of privileged communications to which the consultant was not a party does not waive the privilege.” RBR Global, LLC v. BFG 108, LLC, 2026 WL 3408097 (S.D.N.Y. Nov. 10, 2026).
RBR is a privilege dispute in an alleged breach of contract action.
Under federal law, the attorney-client privilege applies only if all the following are met:
(1) the asserted holder of the privilege is or sought to become a client; (2) the person to whom the communication was made (a) is a member of the bar of a court, or his subordinate and (b) in connection with this communication is acting as a lawyer; (3) the communication relates to a fact of which the attorney was informed (a) by his client (b) without the presence of strangers (c) for the purpose of securing primarily either (i) an opinion on law or (ii) legal services or (iii) assistance in some legal proceeding, and not (d) for the purpose of committing a crime or tort; and (4) the privilege has been (a) claimed and (b) not waived by the client.
Id. at *3, quoting Upjohn Co. v. U.S., 449 U.S. 383, 389 (1981).
The “functional equivalent doctrine” holds that “there is little reason if any to distinguish between a person on the corporation’s payroll and a consultant hired by the corporation if each acts for the corporation and possesses the information needed by attorneys in rendering legal advice.” Id. at *5 (cleaned up).
The RBR court noted that some courts have “expressed skepticism” about recognizing the doctrine. Id. at *5. However, where courts recognize the principle, they have considered the following factors:
(1) whether the consultant had a primary responsibility for a key corporate job; (2) whether the consultant had a continuous and close working relationship with the company’s principals on matters critical to the company’s position in litigation; (3) whether the consultant is likely to possess information possessed by no one else at the company; (4) whether the consultant exercised independent decision-making on the company’s behalf; (5) whether the consultant served as a company representative to third parties; and (6) whether the consultant sought legal advice from corporate counsel to guide his or her work for the company.
Id. at *6 (the “Walsh factors”; citation omitted).
The doctrine is not a privilege. Rather, it is an exception that prevents a finding of waiver by disclosure of privileged information to a consultant. Id. at *8.
On the facts presented, the RBR court determined that H&M failed to provide a factual predicate for holding that the consultant was the functional equivalent of an employee. Id. at *6.
Applying the six factors seriatim, the RBR court assumed that the consultant held “a key corporate job.” However, the purpose of the “close working relationship” was “to effectuate a business transaction.” Id. at *10. The court continued:
Third, even if Monahan were an expert — which the Court cannot find given that the H&M Defendants have not provided his resume or biographical information — they have not detailed what information Monahan possessed that no one else at the BFG Defendants “would not have possessed or could not have developed on their own.” … Fourth, the H&M Defendants do not detail any decisions Monahan “made independently.”
Id. at *10.
As to the fifth and sixth factors, there was no showing of an effort to solicit legal advice. Id. At most, there was showing of the disclosure of non-privileged information to an attorney, and underlying facts are not privileged. Id.
The RBR court concluded: “Ultimately, the H&M Defendants have demonstrated fewer than half of the Walsh factors, and so have not established that Monahan was the functional equivalent or de facto employee of the BFG Defendants.” Id. at *10 (cleaned up).
Assisted by GAI and LLM Technologies per EDRM’s GAI and LLM Policy.

