A federal judge in the Eastern District of Tennessee just handed TCPA defendants a rare procedural win — and it should reframe how operators think about lead documentation. On May 11, 2026, U.S. District Judge Katherine A. Crytzer denied the plaintiff’s Rule 56(d) request in Brockington v. Hume Health, LLC, refusing to defer summary judgment so the plaintiff could fish for more discovery on her consent claim. The decision (2026 WL 1284850) is the kind of small, technical ruling that quietly changes the math on whether a TCPA class action is worth bringing in the first place.
What actually happened
Sheri Butler Brockington sued Hume Health alleging it called and texted her in violation of the TCPA and the National Do Not Call Registry rules. Hume Health moved for summary judgment, attaching its evidence of consent: a Facebook lead form Brockington had filled out, complete with the “SIGN UP” click that allegedly authorized the contact. Instead of opposing the motion on its merits, the plaintiff asked the court to delay summary judgment under Rule 56(d), claiming she needed more discovery to challenge the lead’s authenticity.
Judge Crytzer wasn’t having it. She held that Brockington failed to identify specific facts she expected to find or explain how additional discovery would actually defeat the consent defense. Bare assertions that “more discovery might reveal something” don’t clear the Rule 56(d) bar. The court will now decide the summary judgment motion on the existing record — a record that includes Hume Health’s lead documentation.
Why this matters for operators
For anyone running outbound calling or texting off paid lead sources, the practical lesson is brutal and useful: the quality of your consent record at the moment of capture determines whether a TCPA case lives or dies. Hume Health is in this position because it has a screenshot, a timestamp, an IP address, and a clean audit trail tying Brockington’s number to the form submission. That documentation is what flipped a class action from “discovery nightmare” to “summary judgment in 90 days.”
If your lead capture pipeline can’t produce that artifact on demand for any phone number on any list, you’re a Rule 56(d) request away from being on the wrong side of this ruling. Operators should be auditing three things this week: (1) whether their lead vendors retain raw form-submission data with full metadata, (2) whether that data is retrievable per-number on a one-day SLA, and (3) whether the disclosure language above the submit button actually clears Reyes v. Lincoln Automotive Financial Services and the broader “clear and conspicuous” standard.
The Rule 56(d) angle is the real signal
What’s notable about Brockington isn’t the consent fight itself — that’s still pending. It’s that the court refused to let a TCPA plaintiff use discovery as leverage to extract a settlement. Rule 56(d) fishing expeditions have been one of the most reliable tools in the professional plaintiff playbook: file a thin complaint, survive the motion to dismiss, demand discovery, and let the defense costs do the rest. A court willing to deny that move on a clear record changes the calculus for both sides.
Expect more defendants to push for early summary judgment on consent when they have the receipts. And expect plaintiffs’ counsel to scrutinize lead provenance harder before filing — because the cases where lead data is clean and dated are now the cases that end fastest.
What to do Monday morning
Three concrete actions for operators reading this: First, pull a random sample of 25 phone numbers off your most recent dialer list and try to produce the underlying consent artifact (form, source URL, timestamp, IP, disclosure text shown at submit). If you can’t, escalate to the lead vendor today. Second, get your lead-storage retention policy in writing — many vendors quietly delete raw submission data after 90 days, which is exactly when you need it most. Third, make sure your dialer’s “do not contact” logic is wired to the same source-of-truth that holds consent records, so a revocation request actually propagates.
One operational hedge worth building into your dialing stack: scrub every outbound list against known TCPA plaintiffs before you launch. TCPALitigatorList.com maintains a continuously updated database of numbers tied to professional plaintiffs and frequent TCPA filers, and a five-minute suppression pass against that file is a lot cheaper than a single class certification fight.
Sources
Brockington v. Hume Health, LLC, 2026 WL 1284850 (E.D. Tenn. May 11, 2026); coverage at National Law Review and LitNews.ai.