throbber
FILED
`4/21/2022 4:54 PM
`FELICIA PITRE
`DISTRICT CLERK
`DALLAS CO., TEXAS
`Cassandra Walker DEPUTY
`
`CAUSE NO. DC-19-09573
`
`SHANKAR PRASADDAS,
`
`Plaintiff,
`
`V.
`
`PEPPERSTONE GROUP LIMITED,
`
`Defendants.
`
`CORUGCGPWONUDCOPCO?UO>SN
`
`IN THE DISTRICT COURT OF
`
`DALLAS COUNTY, TEXAS
`
`101ST JUDICIAL DISTRICT
`
`PLAINTIFF’S OBJECTION TO DEFENDANT’S MOTION TO DESIGNATE
`RESPONSIBLE THIRD PARTIES
`
`A defendant may seek to designate a person as a responsible third party by
`filing a motion for leave to designate that person as a responsible third party.
`
`3 og ok
`
`A court shall grant leave to designate the person as a responsible third party
`unless another party files an objection on or before the 15th day after the
`date the motion is served.
`
`tie og ok
`
`If an objection to the motion for leave is timely filed, the court shall grant
`leave to designate the person as a responsible third party unless the
`objecting party establishes: (1) the defendant did not plead sufficient facts
`concerning the alleged responsibility of the person to satisfy the pleading
`requirement of the Texas Rules of Civil Procedure; and (2) after having
`been granted leave to replead, the defendant failed to plead sufficient facts
`concerning the alleged responsibility of the person to satisfy the pleading
`requirements of the Texas Rules of Civil Procedure.
`
`TEX. Civ. PRAC. & REM. CODE § 33.004(a), (f), (g) (emphasis added).
`
`1.
`
`In its Motion to Designate Responsible Third Parties, Defendant Pepperstone
`
`Group Limited has failed to “plead sufficient facts concerning the alleged responsibility” of
`
`Nashith Wadud and CITT Services for the claims asserted by Plaintiff Shankar Das.
`
`2.
`
`Das has asserted six causes of action: (1)a violation of the Texas Sales
`
`Representative Act
`
`(“TSRA”);
`
`(2) breach of contract;
`
`(3) quantum meruit;
`
`(4) promissory
`
`PLAINTIFF’S OBJECTION TO DEFENDANT’S MOTION TO DESIGNATE RESPONSIBLE THIRD PARTIES
`
`PaGE 1
`
`

`

`estoppel; (5) unjust enrichment; and (6) fraud. Pepperstone has failed to state which of these
`
`causes of action Wadud and CITTare allegedly responsible for. That said, the statute governing
`
`the designation of responsible third parties allows Pepperstone to designate Wadud and CITT for
`
`only one of these claims: the fraud claim. Thestatute states: “This chapter applies to... any cause
`
`of action based on tort... or... any action brought under the Deceptive Trade Practices-Consumer
`
`Protection Act... .” TEX. CIv. PRAC. & REM. CODE § 33.002(a). The only claim based on tort
`
`law is the fraud claim. The other claimsare all statutory (but not DTPA), contractual, or quasi-
`
`contractual, equitable claims basedinrestitution.
`
`3.
`
`Also, Pepperstone is not permitted to designate Wadud and CITT as responsible
`
`third parties for the exemplary damages sought by Dasin his fraud claim. The statute continues:
`
`“This chapter does not apply to... a claim for exemplary damages includedin an action to which
`
`this chapter otherwise applies ....” Jd. § 33.002(c)(2). Thus, at the very least, Pepperstone must
`
`replead its motion to clarify that it seeks to designate Wadud and CITT only for Das’s fraud claim
`
`and only for the actual damages sought underthat claim.
`
`4.
`
`But even if Pepperstone clarifies which claimsit is designating Wadud and CITT
`
`for, Pepperstone’s pleading wouldstill be deficient. This is because nowhere in its motion does
`
`Pepperstone assert that Wadud was not acting as an agent of Pepperstone when he and other
`
`Pepperstone employees fraudulently induced Das to work for Pepperstone for free. Das has made
`
`explicit in his live petition that Wadud was Pepperstone’s Director of U.S. Operations and a
`
`financial advisor registered with the Australian Securities and Investments Commission, making
`
`him both an employee and an authorized agent of Pepperstone.
`
`5.
`
`Claims based on an employer-employee relationship, such as that between Wadud
`
`and Pepperstone, are not subject to the third-party-designation statute. See, e.g., Battaglia v.
`
`PLAINTIFF’S OBJECTION TO DEFENDANT’S MOTION TO DESIGNATE RESPONSIBLE THIRD PARTIES
`
`PAGE 2
`
`

`

`Alexander, 93 8.W.3d 132, 144 (Tex. App.—Houston [14th Dist.] 2002, no pet.) (““Common-law
`
`joint-and-several liability rules for partnership, agency, joint venture, and piercing the corporate
`
`veil situations survived the enactment of § 33.013... .” (emphasis added)) rev’d in part on other
`
`grounds 177 S.W.3d 893 (Tex. 2005); N. Am. Van Lines, Inc. v. Emmons, 505.W.3d 103, 122
`
`(Tex. App.—Beaumont 2001, pet denied) (“The proportionate responsibility statute did not do
`
`away with the application of partnership and agency theories .
`
`.
`
`. .” (emphasis added)). This is
`
`because regardless of any allegation or fault on the part of the employer,if the employee wasacting
`
`in the course of his employment, the employer will be held vicariously liable for the actionsofits
`
`employee. See, e.g., Bedford v. Moore, 166 S.W.3d 454, 461 (Tex. App.—Fort Worth 2005, no
`
`pet.).
`
`6.
`
`Thus, unless Pepperstone sufficiently alleges in its motion that Wadud wasnotthe
`
`employee or agent of Pepperstone, the law prohibits Pepperstone from designating Wadud as a
`
`responsible third party because Das has claimed that Wadud acted as the agent for Pepperstone.
`
`In other words, Das has claimed that Wadud’s actions = Pepperstone’s actions. If Pepperstone is
`
`claiming that Wadud was not a Pepperstone agent—and thus that Wadud may be separately
`
`apportioned some percentage of responsibility—Pepperstone must specifically state so in its
`
`motion.
`
`7.
`
`For all these reasons, Das asks that the Court deny Pepperstone’s Motion to
`
`Designate Responsible Third Parties and require Pepperstone to replead.
`
`If Pepperstone’s
`
`repleaded motionis likewise insufficient, Das will object again at that time and ask that the Court
`
`deny Pepperstone’s motion without further opportunities to replead, according to Texas Civil
`
`Practices and Remedies Code § 33.004(g).
`
`PLAINTIFF’S OBJECTION TO DEFENDANT’S MOTION TO DESIGNATE RESPONSIBLE THIRD PARTIES
`
`PAGE3
`
`

`

`Respectfully submitted,
`
`
`/s/ Kush Patel
`
`Kush Patel
`
`State Bar No. 24110869
`patel@kush.law
`Kush.Law
`
`P.O. Box 631247
`Irving, Texas 75063
`Phone: 972.974.5094
`
`
`/s/ Michael A. Holmes
`Michael A. Holmes
`
`State Bar No. 24083191
`Michael@HolmesLG.com
`Holmes Law Group, PLLC
`P.O. Box 38282
`Dallas, Texas 75238
`Phone: 214.444.9533
`
`ATTORNEYSFOR PLAINTIFF
`SHANKAR PRASAD DAS
`
`CERTIFICATE OF SERVICE
`
`I certify that on April 21, 2022 a true and correct copy of the above-described document
`wasserved via eFile on all counsel of record for this case.
`
`
`/s/ Kush Patel
`Kush Patel
`
`PLAINTIFF’S OBJECTION TO DEFENDANT’S MOTION TO DESIGNATE RESPONSIBLE THIRD PARTIES
`
`PaGrE4
`
`

`

`Automated Certificate of eService
`This automated certificate of service was created by the efiling system.
`The filer served this document via email generated by the efiling system
`on the date and to the personslisted below. The rules governing
`certificates of service have not changed. Filers muststill provide a
`certificate of service that complies with all applicable rules.
`
`Trevor Martin on behalf of Trevor Martin
`Bar No. 24109512
`Trevor@HolmesLG.com
`Envelope ID: 63795179
`Status as of 4/22/2022 11:34 AM CST
`
`Associated Case Party: SHANKARPRASADDAS
`
`Shankar PrasadDas S|SENT
`
`Kush Patel [ean[amare[sr
`[ee|[esscon__|AEVEREPT[ET
`ererin|[rrrom|BRET[SET
`
`eweceok[eeriesonaaa[ET
`
`Associated Case Party: PEPPERSTONE GROUP LIMITED
`
`
`
`eschneider@meginnislaw.com|4/21/2022 4:54:16 PM|SENT fMarialsiasoT mislas@pamlaw.com
`
`Ashley Parrish P| aparrish@meginnislaw.com|4/21/2022 4:54:16 PM|SENT
`JamesPhillips po jphillips@mcginnislaw.com|4/21/2022 4:54:16 PM|SENT
`Ikirner@mcginnislaw.com|4/21/2022 4:54:16 PM|SENT
`
`Case Contacts
`
`JEFFREY RSANDBERG 4/21/2022 4:54:16 PM|SENTjsandberg@pamlaw.com
`
`
`4/21/2022 4:54:16 PM|SENT
`
`Rosalinda Hernandez
`rhernandez@mcginnislaw.com|4/21/2022 4:54:16 PM|SENT
`
`Charmaine Schneider
`
`inni
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket