Martin v. TEKsystems Management Incorporated (Fn)

CourtDistrict Court, D. Arizona
DecidedJune 8, 2021
Docket2:20-cv-02192
StatusUnknown

This text of Martin v. TEKsystems Management Incorporated (Fn) (Martin v. TEKsystems Management Incorporated (Fn)) is published on Counsel Stack Legal Research, covering District Court, D. Arizona primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Martin v. TEKsystems Management Incorporated (Fn), (D. Ariz. 2021).

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA 8

Michae l Martin, ) No. CV-20-02192-PHX-SPL ) 9 ) 10 Plaintiff, ) ORDER vs. ) ) 11 ) TEKsystems Management ) 12 Incorporated (Fn), et al., ) 13 ) ) 14 Defendants. )

15 I. BACKGROUND 16 Defendant TEKsystems is a staffing company. (Doc. 1 at ¶ 13). TEKsystems placed 17 Plaintiff Michael Martin as a Network Engineer for Defendant American Airlines, one of 18 TEKsystems’ clients. (Doc. 13 at 2). On November 3, 2020, Plaintiff filed a Complaint in 19 this Court alleging disability discrimination, failure to engage in the interactive process, 20 failure to accommodate, and retaliation under the Americans with Disabilities Act of 1990, 21 42 U.S.C. § 12101 et seq. (“ADA”). (Doc. 1). Before the Court is Defendant TEKsystems’ 22 Motion to Compel Arbitration (Doc. 13). 23 When TEKsystems first hired Plaintiff, Plaintiff was required to sign, and did 24 electronically sign, a “Mutual Arbitration Agreement.” (Doc. 13 at 3). The agreement states 25 in pertinent part: 26 [A]ll disputes, claims, complaints, or controversies . . . including . . . discrimination and/or harassment claims; 27 retaliation claims; . . . and any other claim under any federal, 28 state, or local statute, constitution, regulation, rule, ordinance, or common law arising out of and/or directly or indirectly 1 related to my . . . employment with the Company . . . are subject 2 to confidential arbitration pursuant to the terms of this Agreement and will be resolved by Arbitration and NOT by a 3 court or jury. 4 (Doc. 13-1 at ¶ 7). 5 Plaintiff alleges that he “had never seen the alleged arbitration agreement and 6 denie[s] signing it.” (Doc. 16 at 2). Plaintiff also argues that “American Airlines, the other 7 Defendant, is not a party to the arbitration agreement and has answered the Complaint” so 8 “the Court should stay [the TEKsystems] claims rather than dismiss the action” so his 9 claims against American can proceed. (Doc. 16 at 1). Plaintiff further asserts he agreed he 10 “would stipulate to move his claims against TEKsystems only (not his claims against 11 American Airlines) to arbitration but only if Mr. Martin and TEKsystems could stipulate 12 to certain related issues,” but that a stipulation was never reached. (Doc. 16 at 2) (emphasis 13 in original). 14 II. LEGAL STANDARD 15 “The standard the court applies in making the arbitrability determination is similar 16 to the summary judgment standard, and the court should review the record to determine if 17 the party opposing arbitration has raised any triable issue of fact.” The O.N. Equity Sales 18 Co. v. Thiers, 590 F. Supp. 2d 1208, 1211 (D. Ariz. 2008). “The court does not require an 19 evidentiary hearing when the underlying factual circumstances which are relevant to the 20 court’s determination of arbitrability are undisputed.” Id. “An order to arbitrate . . . should 21 not be denied unless it may be said with positive assurance that the arbitration clause is not 22 susceptible of an interpretation that covers the asserted dispute. Doubts should be resolved 23 in favor of coverage.” United Steelworkers of America v. Warrior & Gulf Navigation Co., 24 363 U.S. 574, 582–83 (1960). 25 III. ANALYSIS 26 In determining whether a motion to compel arbitration should be granted, the court 27 generally “ask[s] only (1) whether there is a valid arbitration agreement and (2) whether 28 1 the particular dispute falls within the terms of that agreement.” Faber v. Menard, Inc., 367 2 F.3d 1048, 1052 (8th Cir. 2004). Here, Plaintiff does not dispute that his asserted claims 3 fall within the arbitration clause; the only issue is whether the agreement is valid. 4 A. Enforceability of Arbitration Agreement 5 1. E-Signature 6 Plaintiff first argues his e-signature is not binding and enforceable under the Arizona 7 Electronic Transactions Act (“AETA”), Ariz. Rev. Stat. §§ 44-7000-7052. (Doc. 16 at 5). 8 Under the AETA, an electronic signature is only secure if it was: (1) “Unique to the person 9 using it,” (2) “Capable of verification,” (3) “Under the sole control of the person using it,” 10 and (4) “Linked to the electronic record to which it relates in such a manner that if the 11 record were changed the electronic signature would be invalidated.” Ariz. Rev. Stat. § 12 44-7031. 13 Plaintiff argues that TEKsystems “provides no evidence showing that it 14 electronically verified that Mr. Martin signed the document.” (Doc. 16 at 5). Plaintiff relies 15 on Smith v. Rent-A-Ctr., Inc., No. 118-CV-01351-LJOJLT, 2019 WL 1294443 (E.D. Cal. 16 Mar. 21, 2019) for the proposition that Plaintiff’s electronic signature here is not binding. 17 However, not only does that case interpret California law and not Arizona law, but it is 18 also distinguishable. There, the court specifically noted that “evidence of use of a unique, 19 secure username and password may sufficiently authenticate a signature when that 20 signature is a typed name inputted by the user.” Id. at *5. In fact, the court also noted that 21 “the act of inputting a username and password, itself, has been found sufficient to constitute 22 an electronic signature.” Id. However, the court found that the plaintiff’s signature was not 23 sufficiently authenticated because the defendant’s affidavits failed to properly explain the 24 authentication process. The court explained: 25 Nowhere in this statement does [Defendant] explain how he inferred that it was Plaintiff who created and entered the 26 password, how he ascertained that the electronic signature was 27 the act of Plaintiff, or how he determined that the form was signed on October 4, 2016. No steps are detailed; no audit trail 28 discussed. It is, in fact, entirely unclear at what point [Plaintiff] entered his password in order to sign the agreement, and 1 whether creating his password and later signing the arbitration 2 agreement were two of several steps in his onboarding or the only onboarding steps he was asked to complete. There is no 3 discussion of timestamps or IP addresses. There is also no 4 mention of Plaintiff’s username. 5 Id. at *6. Instead, the affidavit “summarily assert[ed] that ‘the [Electronic Signature and 6 Acknowledgment Agreement] process involves the employee creating a unique and secret 7 password, which serves as the employee’s electronic signature. [Plaintiff] signed the 8 Electronic Signature and Acknowledgement Agreement by entering his unique and secret 9 password.’” Id. 10 Here, TEKsystems’ onboarding system requires candidates to “create a unique 11 username and password, as well as three security questions, which are asked whenever the 12 candidate logs into his or her invitation.” (Doc. 19 at 3). Furthermore, the affidavit of 13 Defendant’s Regional Human Resources Manager, Allison Schenk, details the process by 14 which the electronic signatures are authenticated. (Doc. 13-1). For example, Ms. Scheck 15 answers the question of “how [s]he inferred that it was Plaintiff who created and entered 16 the password”: the Onboarding Automation system, before allowing the individual to 17 create a username and password, requires that the employee “provide their first, middle, 18 and last name, social security number, date of birth, gender, race, veteran status, home 19 address, home and cell phone number, email address, marital status, emergency contact 20 information, and tax withholdings.” (Doc. 13-1 at ¶ 4).

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

Related

Kilgore v. KeyBank, National Ass'n
673 F.3d 947 (Ninth Circuit, 2012)
Merrill Lynch Investment Managers v. Optibase, Ltd.
337 F.3d 125 (Second Circuit, 2003)
Brown v. EF Hutton & Co., Inc.
610 F. Supp. 76 (S.D. Florida, 1985)
The ON EQUITY SALES CO. v. Thiers
590 F. Supp. 2d 1208 (D. Arizona, 2008)
City of Cottonwood v. James L. Fann Contracting, Inc.
877 P.2d 284 (Court of Appeals of Arizona, 1994)
Medivas, LLC v. Marubeni Corporation
741 F.3d 4 (Ninth Circuit, 2014)
Paige Martin v. Gary Yasuda
829 F.3d 1118 (Ninth Circuit, 2016)
June Newirth v. Aegis Senior Communities, LLC
931 F.3d 935 (Ninth Circuit, 2019)
Sun Valley Ranch 308 Ltd. Partnership v. Robson
294 P.3d 125 (Court of Appeals of Arizona, 2012)
Clark v. Renaissance West, LLC
307 P.3d 77 (Court of Appeals of Arizona, 2013)
Dueñas v. Life Care Centers of America, Inc.
336 P.3d 763 (Court of Appeals of Arizona, 2014)
Ortiz v. Hobby Lobby Stores, Inc.
52 F. Supp. 3d 1070 (E.D. California, 2014)
Belke v. Merrill Lynch, Pierce, Fenner & Smith
693 F.2d 1023 (Eleventh Circuit, 1982)
Fisher v. A.G. Becker Paribas Inc.
791 F.2d 691 (Ninth Circuit, 1986)

Cite This Page — Counsel Stack

Bluebook (online)
Martin v. TEKsystems Management Incorporated (Fn), Counsel Stack Legal Research, https://law.counselstack.com/opinion/martin-v-teksystems-management-incorporated-fn-azd-2021.