Bradley Talmadge Livingston v. GardaWorld, LLC, et al.

CourtDistrict Court, D. New Jersey
DecidedDecember 4, 2025
Docket2:23-cv-23006
StatusUnknown

This text of Bradley Talmadge Livingston v. GardaWorld, LLC, et al. (Bradley Talmadge Livingston v. GardaWorld, LLC, et al.) is published on Counsel Stack Legal Research, covering District Court, D. New Jersey primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Bradley Talmadge Livingston v. GardaWorld, LLC, et al., (D.N.J. 2025).

Opinion

UNITED STATES DISTRICT COURT DISTRICT OF NEW JERSEY

BRADLEY TALMADGE LIVINGSTON,

Civil Action No. 23-23006 (JXN)(SDA) Plaintiff,

v. OPINION GARDAWORLD, LLC, et al.,

Defendants.

NEALS, District Judge Before the Court is pro se Plaintiff Bradley Talmadge Livingston’s (“Plaintiff”) timely objections (ECF No. 214) to Magistrate Judge Stacey D. Adams’ May 13, 2025 Report and Recommendation (“R&R”) recommending dismissal of Plaintiff’s Complaint without prejudice for failure to prosecute and discovery violations (ECF No. 204). The Court has reviewed the R&R, Plaintiff’s objections, and the record. For the reasons that follow, Plaintiff’s objections are DENIED, the R&R is AFFIRMED, and the Complaint is DISMISSED without prejudice. I. BACKGROUND Plaintiff, a frequent filer in this District,1 filed an employment discrimination lawsuit in this Court on December 11, 2023. (See Compl., ECF No. 1.) He alleges his former employers, GardaWorld LLC and Emanuel Johnson (“Defendants”), changed his hours and fired him because of his race and in retaliation for making complaints about other employees. (Id. at *11.2)

1 See Livingston v. Baldwin, No. 25-2715; Livingston v. United States, No. 25-2328; Livingston v. Uber, No. 24-5839; Livingston v. City of Englewood, No. 24-3696; Livingston v. Gallina, No. 24-8862; Livingston v. Borough of Elmwood Park, No. 24-1210; Livingston v. Hibbert-Livingston, No. 24-1216; Livingston v. Williams, No. 24-1056; Livingston v. Securitas Critical Infrastructure Servs., Inc., No. 24-5838; Livingston v. Thrive at Montvale, No. 23-23004. 2 Pincites preceded by an asterisk (*) indicate pagination according to CM/ECF headers. Before Defendants answered, “Plaintiff began blanketing the docket with countless, baseless filings and applications, such as requests for default (ECF Nos. 16, 17, 20), requests for final judgment (ECF No. 9), and letters purporting to provide the Court with ‘evidence.’ (ECF Nos. 13, 14).” (R&R at 2). Plaintiff’s “constant submissions only increased” after Defendants filed

an answer. (Id.) A. Motion to Dismiss for Discovery Violations Judge Adams held an initial pretrial conference on July 25, 2024, and entered a Pretrial Scheduling Order the next day. (See id.; Scheduling Order, ECF No. 54.) The judge “required initial disclosures to be served by August 5, 2024, discovery requests to be served by August 9, 2024, and discovery responses to be served in accordance with the time frames set by the Federal Rules.” (R&R at 2; see also Scheduling Order.) Judge Adams set January 31, 2025, as the close of fact discovery. (Scheduling Order.) Defendants timely served their initial disclosures and discovery requests; Plaintiff did not. (See Defs.’ Moving Br. 2, ECF No 127-1.) Despite numerous deficiency letters, (see, e.g., ECF Nos. 127-2, 127-3), a court order directing Plaintiff to respond,

(ECF No. 57), and a motion to compel, (ECF No. 70), Plaintiff submitted evasive, cryptic, and incomplete answers two months late, (see, e.g., ECF No. 74), and failed to provide responsive documents. Following a December 10, 2024 status conference, Judge Adams ordered Plaintiff to serve his initial disclosures and supplement his deficient responses by December 20, 2024. (Am. Scheduling Order, ECF No. 105.) Judge Adams warned that granting Defendants leave to move for sanctions, up to and including dismissal, would result from Plaintiff’s failure to comply. (Id.) Plaintiff provided supplemental responses to Defendants on December 19, 2024. (See ECF No. 127-4.) But Plaintiff’s “supplemental responses were again deficient as Plaintiff still failed to respond to many of the requests, failed to assert individual objections to each interrogatory, and/or failed to provide responsive documents.” (R&R at 3.) By January 13, 2025, Plaintiff had not served his initial disclosures, prompting Defendants to file a motion to dismiss for discovery violations. (See Defs.’ Moving Br.) Plaintiff filed two

letters in opposition. The first was “nearly indecipherable,” but broadly alleged Defendants’ discovery requests were designed to humiliate him. (R&R at 4; see also ECF No. 128.) The second “was couched as a response to a motion to dismiss for failure to state a claim” and did not address any of Plaintiff’s discovery violations. (R&R at 4; see also ECF No. 154.) B. Order to Show Cause At the December 10, 2024 status conference, Judge Adams scheduled another conference for February 5, 2025. (Am. Scheduling Order.) The judge ordered the conference be held in person “due to ongoing concerns about case management, Plaintiff’s repeated improper and often incomprehensible filings, Plaintiff’s failure to meet his discovery obligations, and overall difficulties dealing with Plaintiff during the virtual conference.” (R&R at 4.)

Plaintiff lives in Maryland. (Id. at 5.) Upon hearing he would have to appear in person for the February 5 status conference, Plaintiff “became noticeably agitated.” (Id.) From then on, Plaintiff “began a campaign of filing letters and applications with the Court offering countless excuses to avoid appearing in Court, from claiming he suffers from a variety of disabilities that prevent him from traveling, to seeking recusal of the undersigned, to alleging unfair treatment.” (Id.) In total, Plaintiff made over 100 filings. (Id. at 5, n.2.) Plaintiff requested a sixty-day adjournment of the February 5 status conference to “retain counsel.” (ECF No. 137.) Plaintiff later requested future conferences be held virtually because he could not drive long distances anymore “due to health issues and suffering with dizziness.” (ECF No. 140.) Following both requests, Judge Adams granted Plaintiff a sixty-day adjournment, stating “[t]he status conference is rescheduled for April 2, 2025 at 2:00 p.m. IN PERSON.” (ECF No. 138.) On April 1, 2025, Plaintiff emailed Defendants requesting to adjourn the April 2 status conference “due to a medical appointment.”3 (ECF No. 147-1.) On the morning of April 2,

Defendants provided Plaintiff’s email to Judge Adams. (ECF No. 147.) The judge viewed Plaintiff’s claim of having a medical appointment with skepticism because: (1) Plaintiff raised his purported disabilities and inability to travel for the first time only after the judge required him to appear in person (Omnibus Scheduling Order 4, ECF No. 201); (2) the limited medical documentation Plaintiff provided (ECF Nos. 152, 166) did not indicate he had “any limitations on his ability to attend court, travel or engage in activities,” (Omnibus Scheduling Order 5); and (3) Plaintiff’s requested accommodation, “that he be permanently excused from any required in person Court appearances,” was not reasonable, (Id.) Accordingly, the April 2, 2025 status conference proceeded as scheduled, but Plaintiff did not attend. (R&R at 6.)

Later that day, Judge Adams ordered Plaintiff to show cause why he should not be sanctioned for failing to attend the status conference. (ECF No. 165.) She scheduled oral argument on the Order to Show Cause (“OTSC”) for April 28, 2025. (Id.) The judge warned that if Plaintiff failed to appear in person on April 28, she would issue an R&R recommending the matter be dismissed for Plaintiff’s failure to comply with court orders and failure to prosecute. (Id.) Plaintiff filed two responses. First, Plaintiff reiterated his claim that he could not attend the April 2, 2025 status conference because of health issues. (ECF No. 166.) Plaintiff attached a

3 Plaintiff filed the same letter on the docket on April 1, but it was not uploaded until April 3. (ECF No. 157.) Judge Adams noted that, to the extent any of Plaintiff’s filings were late, it was “almost always” due to “(i) Plaintiff putting one date on the letter but not sending it to the Court until a later date, (ii) Plaintiff not sending it to the Court at all . . .

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

Related

Thomas v. Arn
474 U.S. 140 (Supreme Court, 1986)
Erickson v. Pardus
551 U.S. 89 (Supreme Court, 2007)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Karen Malleus v. John George
641 F.3d 560 (Third Circuit, 2011)
Kelley Mala v. Crown Bay Marina
704 F.3d 239 (Third Circuit, 2013)
Phillips v. County of Allegheny
515 F.3d 224 (Third Circuit, 2008)
Makky v. Chertoff
541 F.3d 205 (Third Circuit, 2008)
Briscoe v. Klaus
538 F.3d 252 (Third Circuit, 2008)
Fowler v. UPMC SHADYSIDE
578 F.3d 203 (Third Circuit, 2009)
Opta Systems, LLC v. Daewoo Electronics America
483 F. Supp. 2d 400 (D. New Jersey, 2007)
Heather Hoffman v. Palace Entertainment
621 F. App'x 112 (Third Circuit, 2015)
John Jean-Pierre v. Angela Schwers
682 F. App'x 145 (Third Circuit, 2017)
Anthony Hildebrand v. County of Allegheny
923 F.3d 128 (Third Circuit, 2019)
DLJ Mortgage Capital, Inc. v. Ana Sheridan
975 F.3d 358 (Third Circuit, 2020)
Davis v. Wells Fargo, U.S.
824 F.3d 333 (Third Circuit, 2016)

Cite This Page — Counsel Stack

Bluebook (online)
Bradley Talmadge Livingston v. GardaWorld, LLC, et al., Counsel Stack Legal Research, https://law.counselstack.com/opinion/bradley-talmadge-livingston-v-gardaworld-llc-et-al-njd-2025.