Roush v. Akal Security Inc

District Court, E.D. Washington·Decided October 9, 2020·No. 2:17-cv-00358·Unknown

Opinion

1 U.S. DISTRICT COURT EASTERN DISTRICT OF WASHINGTON

Oct 09, 2020 2 SEAN F. MCAVOY, CLERK 3

5 UNITED STATES DISTRICT COURT EASTERN DISTRICT OF WASHINGTON 6

7 RONALD W. ROUSH and JAMES H. HUNTER, NO: 2:17-CV-358-RMP 8 Plaintiffs, ORDER GRANTING 9 DEFENDANT’S SUMMARY v. JUDGMENT MOTION AND 10 DENYING PLAINTIFFS’ PARTIAL AKAL SECURITY, INC, SUMMARY JUDGMENT MOTION 11 Defendant. 12

13 BEFORE THE COURT is a Motion for Partial Summary Judgment from 14 Plaintiffs Ronald Roush and James Hunter, ECF No. 86, and a Motion for Summary 15 Judgment from Defendant Akal Security, Inc. (“Akal”), ECF No. 113, and the 16 parties’ Stipulated Voluntary Dismissal of Counterclaims, ECF No. 132. The Court 17 has reviewed the parties’ filings with respect to all motions, the remaining record, 18 the relevant law, and is fully informed. 19 BACKGROUND 20 Unless otherwise noted, the following background facts are undisputed. On 21 July 23, 2012, the United States Transportation Security Administration (“TSA”) 1 issued Solicitation number HSTS05-12-R-SPP038 (the “Solicitation”) for security 2 services at the Kansas City International Airport (“MCI”) in Missouri. ECF No. 108

3 at 2. Plaintiffs contend that Akal contacted them by telephone on or around 4 September 5, 2012, to solicit their names and professional qualifications for purposes 5 of submitting a bid in response to the Solicitation. ECF No. 112 at 4; see also ECF

6 Nos. 31-1 and 31-2. Defendant maintains that Defendant already had Plaintiffs’ 7 names, but does not dispute that Defendant and its subcontractor, AWD Management 8 Services, Inc. (“AWD”) contacted Plaintiffs for telephone interviews to “determine 9 whether to offer Plaintiffs a position to work at MCI.” ECF No. 108 at 3.

10 Subsequent to Plaintiffs’ telephone conversations with Akal and AWD 11 representatives, on or around September 5, 2012, Roush and Hunter submitted their 12 resumes, detailing their experience in the aviation security field, to Akal via

13 subcontractor AWD. ECF Nos. 86-4 at 1; 86-5 at 1; and 108 at 3. 14 Akal submitted its bid proposal to TSA on or before the submission deadline 15 of March 4, 2013. ECF Nos. 74 at 4; 112 at 4. Akal’s bid proposal contained 16 Plaintiffs’ names and professional qualifications as proposed “Key Personnel.” ECF

17 No. 112 at 4−5. 18 TSA awarded the MCI contract to Akal on February 24, 2014. ECF Nos. 20 19 at 5; 74 at 5. Through a different subcontractor, Synergy Solutions, Inc.

20 (“Synergy”), Akal hired Plaintiffs for their respective positions at MCI. ECF Nos. 21 74 at 18; 86-14; and 86-15. 1 Plaintiffs both declare for purposes of these motions that they became aware 2 that Akal had used their names and credentials in its bid proposal on February 24,

3 2014, when they reviewed the MCI contract award and saw that they were included 4 in Section 1.7, “Key Personnel and Facilities.” ECF Nos. 86-4 at 1; 86-5 at 1. Both 5 Plaintiffs declare that they did not give Akal consent to use their names and

6 credentials in its bid proposal. Id. Plaintiff Roush testified at deposition that 7 “arguably” he would have “been okay” with his name and credentials being included 8 in the bid proposal had he and Hunter “gone ahead and worked on the project.” ECF 9 No. 125-1 at 14.

10 By mid-March 2014, a competitor of Akal’s filed a protest contesting the 11 award of the contract to Akal, and TSA issued a stop work order delaying the start of 12 the contract. ECF Nos. 74 at 18; 125-1 at 16−17. Plaintiffs were aware of the

13 protest and understood that Akal could not start working on the MCI project until the 14 stop work order was removed. See ECF Nos. 116-12 at 1; 125-1 at 14. Plaintiffs did 15 not receive compensation from Akal before or after the contract award on February 16 24, 2014. Email correspondence from the President of Synergy to Plaintiffs dated

17 March 19, 2014, indicates that Plaintiffs were exploring avenues of receiving 18 income from Akal during the bid protest, and Synergy was open to that discussion. 19 ECF No. 109-9. Similarly, Roush recalled a conversation with the Synergy

20 President from early August 2014, in which she agreed to submit to Akal the 21 1 transition expenses that Plaintiffs believed should be allowable, asserting that she 2 could make no promises. ECF No. 109-1 at 14.

3 At some point in August 2014, Plaintiffs consulted with a lawyer about the 4 possibility of pursuing legal action against Akal. ECF Nos. 116-2 at 14; 116-3 at 5 1−2. Roush testified at his deposition that Plaintiffs’ inquiry with an attorney was

6 precipitated by “the fact that [Plaintiffs] were named as key personnel and had 7 essentially been in limbo for, at this point . . . five months, six months, since the stop 8 work order had been put into place . . . .” ECF No. 116-2 at 15. 9 In a letter to Akal’s subcontractor Synergy dated September 5, 2014,

10 Plaintiffs’ then-counsel1 conveyed “the sense of disappointment [his] clients share in 11 having to retain legal counsel to resolve their grievances over what has transpired 12 thus far with their employment relationship with Synergy.” ECF No. 109-2 at 1.

13 Plaintiffs’ counsel expanded that Plaintiffs believed, at the time of the letter, that 14 Synergy should have taken a “pro-active position in securing their continued 15 commitment” to Synergy with respect to the MCI security contract, but instead had 16 “inappropriately shifted” “certain inequities and burdens” to Plaintiffs, causing them

17 “significant financial hardships” waiting for a start date while the protest proceeded 18 at the United States Court of Claims. Id. at 1−2. Plaintiffs’ counsel conveyed that 19

20 1 Plaintiffs have not appeared through counsel in the present litigation and instead 21 1 the status quo at the time of the letter was “unacceptable” to Plaintiffs, and “if 2 suitable agreements cannot be reached that resolve all my clients’ issues, they will

3 have no alternative but to revoke their acceptance of employment, and to actively 4 seek employment with organizations that will better appreciate their expertise.” Id. 5 at 2. The September 5, 2014 letter from Plaintiffs’ counsel alleged no misconduct

6 by Akal in naming Plaintiffs as key personnel in the bid, but asserted that including 7 Plaintiffs as key personnel risked certain ramifications for Synergy and Akal: 8 Of course upon the revocation of their acceptance of employment, Synergy will be required to inform the Contracting Officer that the Key 9 Personnel identified in the Bid Contract have changed. I cannot say with any certainty that such notice will void the Bid, but it is certainly 10 likely that such change will delay the award while new Key Personnel are located and the appropriate vetting process is completed. I should 11 think the potential for another Stop Order is a distinct possibility as well. I present my clients [sic] intentions without cloud of threat, and 12 they should not be received as such. However, my clients' circumstances have left them little alternative but to place the issues 13 squarely before Synergy so that it can do what it must do under the circumstances. Stated another way, my clients are going to make certain 14 business decisions that are in their best interests. They expect no less from Synergy and Akal. Should Synergy and Akal find it in their best 15 interests to reach an agreement with Messrs. Hunter and Roush that will keep them as Key Personnel, my clients are amenable to reaching 16 agreements to all's mutual benefit.

17 . . . The uncertainty that the parties find themselves in is directly related to the lack of a written agreement that could have provided for the types 18 of contingencies that currently exist. Synergy made a business decision not to enter into an employment contract with my clients.

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

Roush v. Akal Security Inc, (E.D. Wash. 2020).

Roush v. Akal Security Inc (Roush v. Akal Security Inc) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Walker v. Armco Steel Corp.
446 U.S. 740 (Supreme Court, 1980)
Anderson v. Liberty Lobby, Inc.
477 U.S. 242 (Supreme Court, 1986)
Lujan v. National Wildlife Federation
497 U.S. 871 (Supreme Court, 1990)
Gazija v. Nicholas Jerns Co.
543 P.2d 338 (Washington Supreme Court, 1975)
Bailie Communications, Ltd. v. Trend Business Systems, Inc.
810 P.2d 12 (Court of Appeals of Washington, 1991)
Hibbard v. Gordon, Thomas, Honeywell, Malanca & O'Hern
826 P.2d 690 (Washington Supreme Court, 1992)
Huss v. United States
738 F. Supp. 1098 (W.D. Michigan, 1990)
Eastwood v. Cascade Broadcasting Co.
722 P.2d 1295 (Washington Supreme Court, 1986)
Kenneth & Kelly Emerson, Apps. v. Island County, Resp.
371 P.3d 93 (Court of Appeals of Washington, 2016)
Dezmond Emeson, V Dept. Of Corrections
376 P.3d 430 (Court of Appeals of Washington, 2016)
Jerry Newmaker v. City of Fortuna
842 F.3d 1108 (Ninth Circuit, 2016)
Rhod-A-Zalea & 35th, Inc. v. Snohomish County
136 Wash. 2d 1 (Washington Supreme Court, 1998)
Kloepfel v. Bokor
66 P.3d 630 (Washington Supreme Court, 2003)
1000 Virginia Ltd. Partnership v. Vertecs Corp.
158 Wash. 2d 566 (Washington Supreme Court, 2006)
Young v. Young
164 Wash. 2d 477 (Washington Supreme Court, 2008)
Cox v. Oasis Physical Therapy, PLLC
153 Wash. App. 176 (Court of Appeals of Washington, 2009)