Weiss v. Loomis, Sayles & Co., Inc.

CourtMassachusetts Appeals Court
DecidedJanuary 23, 2020
DocketAC 18-P-1404
StatusPublished

This text of Weiss v. Loomis, Sayles & Co., Inc. (Weiss v. Loomis, Sayles & Co., Inc.) is published on Counsel Stack Legal Research, covering Massachusetts Appeals Court primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Weiss v. Loomis, Sayles & Co., Inc., (Mass. Ct. App. 2020).

Opinion

NOTICE: All slip opinions and orders are subject to formal revision and are superseded by the advance sheets and bound volumes of the Official Reports. If you find a typographical error or other formal error, please notify the Reporter of Decisions, Supreme Judicial Court, John Adams Courthouse, 1 Pemberton Square, Suite 2500, Boston, MA, 02108-1750; (617) 557- 1030; SJCReporter@sjc.state.ma.us

18-P-1404 Appeals Court

JOEL WEISS vs. LOOMIS, SAYLES & COMPANY, INC., & another.1

No. 18-P-1404.

Suffolk. September 11, 2019. - January 23, 2020.

Present: Blake, McDonough, & Hand, JJ.

Independent Contractor Act. Practice, Civil, Directed verdict.

Civil action commenced in the Superior Court Department on January 30, 2014.

The case was tried before Christine M. Roach, J.

Stephen S. Churchill (Brant Casavant also present) for the plaintiff. James W. Bucking (Allison L. Anderson also present) for the defendants. Stephen T. Melnick, Jennifer M. Duke, & Mary K. Sexton, for Massachusetts Technology Leadership Council, Inc., amicus curiae, submitted a brief.

McDONOUGH, J. Joel Weiss filed a single-count complaint in

the Superior Court, alleging that the defendants, Loomis Sayles

1 Loomis, Sayles & Company, L.P. 2

& Company, Inc., and Loomis Sayles & Company, L.P.

(collectively, Loomis), misclassified him as an independent

contractor rather than an employee. See G. L. c. 149, §§ 148B

(§ 148B or independent contractor statute), 150. In the middle

of the jury trial, after Loomis had moved for a directed verdict

and had begun presenting evidence in its defense, the judge

directed a verdict in favor of Loomis, the party with the burden

of proof. We reverse.2

Evidence. In assessing the judge's order allowing Loomis's

motion for a directed verdict, we summarize the evidence in the

light most favorable to Weiss, the nonmoving party, while

drawing all reasonable inferences in his favor. See Donaldson

v. Farrakhan, 436 Mass. 94, 96 (2002). In 2010, a recruiter at

Eliassen Group, LLC (Eliassen), a large information technology

staffing firm, contacted Weiss about certain project-based work

at Loomis, a financial services company.3 Weiss, a software

engineer with significant experience in the financial sector,

was interested in the engagement. After Weiss signed, as

2 We acknowledge the amicus brief submitted by the Massachusetts Technology Leadership Council, Inc.

3 More specifically, Loomis is an asset management company that creates and manages custom investment portfolios for institutional clients. The particular project called for an individual to take over an application called Risk Insite, and to support and update it as necessary. 3

president of JoSol, Inc. (JoSol),4 an independent contractor

agreement (initial contractor agreement) with Eliassen, he

interviewed with Loomis supervisors, Kevin McGuire and Luke

Antolini. A decision was made that Weiss was a good fit for

Loomis.

On August 4, 2010, Loomis entered into a "professional

services vendor agreement" with Eliassen for "Joel Weiss for

technology services." The initial contractor agreement between

Weiss's company, JoSol, and Eliassen ran for three months. The

parties subsequently extended the agreement on several

occasions. The only JoSol employee authorized to provide

services to Loomis was Weiss. On February 1, 2013, Loomis and

Eliassen entered into a second "professional services vendor

agreement" for "Joel Weiss for Technology Services." That

contract, which ran through December 31, 2013, contained

language stating that Weiss was "free to accept engagements from

others during the term of this Agreement, so long as such

actions [did] not impair [his] ability to perform his . . .

services to Loomis Sayles." If Loomis had extended an offer of

4 JoSol, Weiss's preexisting consulting company, had just two employees: Weiss and his wife, Sarah. Weiss opted to contract with Eliassen through JoSol because the corporation-to- corporation arrangement was a better overall financial deal than a direct relationship with Eliassen. Before the Loomis engagement, Eliassen required Weiss to furnish proof that JoSol was a legitimate business. Notably, Loomis never learned of the existence of JoSol. 4

employment, Weiss would have accepted it; Loomis provided its

employees with a more generous benefit package than those

available through JoSol and Eliassen. Weiss, however, was not

given that choice.

In September 2010, Weiss commenced work in Loomis's

technology group. Working in teams, the Loomis managers in the

group created and oversaw projects to meet the needs of the

Loomis investment professionals.5 As a member of McGuire's team,

Weiss worked on a number of these team projects, creating and

fixing information technology applications. Weiss also worked

on several projects of various lengths for other managers,

including one spearheaded by John Gidman, Loomis's chief

information officer (CIO). In total, Weiss worked on at least

fifteen Loomis projects.

Weiss reported, among others, to McGuire. During their

daily interactions, McGuire "would give [Weiss] direction" and

Weiss would bring issues to McGuire. The "powers that be" also

assigned required tasks to Weiss as part of his daily job.

Weiss worked directly with the Loomis employees who used the

applications, assisting with specific issues and upgrades.

5 The investment professionals (portfolio managers, analysts, and traders) made up only thirty-five to forty percent of Loomis's total workforce of 680. 5

Loomis assigned Weiss to a cubicle directly across from

McGuire's office and provided Weiss with a desk, computer,

office supplies, a badge allowing building access, a Loomis

picture identification card, a Loomis telephone number, and a

Loomis e-mail address. Although Weiss had no set work hours,

"the conventional wisdom" was that he should be in the office

during business hours. For the first two years, Weiss worked

five days per week in the office; during his final year, he

worked at home, as did "most of the people [he] knew [at

Loomis]," on Fridays and during holiday periods. When he worked

at home, he used his personal laptop computer, which someone at

Loomis helped him partition to keep his business work separate

from his personal matters. He always alerted his Loomis

supervisor to his whereabouts.

Weiss attended at least a couple of team-wide and project-

specific meetings per week. All members of the team -- Loomis

employees and contractors -- attended the team-wide meetings.6

The contractors frequently communicated with Loomis managers and

worked out the technical details of projects with them. On many

occasions, Loomis converted contractors into employees.

6 Loomis referred to the contractors, among other designations, as "consultants," "developers," "temps," and "vendors." 6

Each week, Weiss submitted time sheets signed by McGuire to

Eliassen, which paid JoSol seventy-five dollars per hour; and

from those proceeds, JoSol paid Weiss a salary.7 Loomis paid

Eliassen $104 per hour for Weiss's services. Loomis approved

some of the contractors' direct requests for rate increases.

In Weiss's first year, McGuire had no objections to Weiss

working overtime, and Weiss was permitted to work as many hours

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Sebago v. Boston Cab Dispatch, Inc.
28 N.E.3d 1139 (Massachusetts Supreme Judicial Court, 2015)
Chambers v. RDI Logistics, Inc.
65 N.E.3d 1 (Massachusetts Supreme Judicial Court, 2016)
Carey v. GateHouse Media Massachusetts I, Inc.
94 N.E.3d 420 (Massachusetts Appeals Court, 2018)
Donaldson v. Farrakhan
436 Mass. 94 (Massachusetts Supreme Judicial Court, 2002)
Athol Daily News v. Board of Review of the Division of Employment & Training
786 N.E.2d 365 (Massachusetts Supreme Judicial Court, 2003)
Chapman v. Katz
448 Mass. 519 (Massachusetts Supreme Judicial Court, 2007)
Somers v. Converged Access, Inc.
911 N.E.2d 739 (Massachusetts Supreme Judicial Court, 2009)
Depianti v. Jan-Pro Franchising International, Inc.
465 Mass. 607 (Massachusetts Supreme Judicial Court, 2013)
Brunelle v. W.E. Aubuchon Co.
804 N.E.2d 955 (Massachusetts Appeals Court, 2004)
Claudio v. City of Chicopee
965 N.E.2d 209 (Massachusetts Appeals Court, 2012)

Cite This Page — Counsel Stack

Bluebook (online)
Weiss v. Loomis, Sayles & Co., Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/weiss-v-loomis-sayles-co-inc-massappct-2020.